Embeddin Tools

[hypersniper05]

Pre-submission Checklist

• I have verified this would not be more appropriate as a feature request in a specific repository
• I have searched existing discussions to avoid duplicates

Your Idea

For many tools, it would be easier for the LLM to query the server for the appropriate tool to use using a cosine similarity search. I have tested this using plain old JSON function calling and it works great and also minimizes the tokens sent to the endpoint.

Scope

• Protocol Specification
• SDK Features
• Documentation
• Developer Experience
• Other

[PederHP]

This should be made as a suggestion to the MCP spec instead. I have an open proposal for a new capability which could do this (in fact tool filtering is one of the examples I used). I agree that RAG techniques to narrow down tool sets to avoid overloading models when you're working with a very large number of tools is a very useful technique in some cases.

I don't think SDKs should implement such features until/if they're part of the protocol spec.

modelcontextprotocol/specification#142

[hypersniper05]

This should be made as a suggestion to the MCP spec instead. I have an open proposal for a new capability which could do this (in fact tool filtering is one of the examples I used). I agree that RAG techniques to narrow down tool sets to avoid overloading models when you're working with a very large number of tools is a very useful technique in some cases.

I don't think SDKs should implement such features until/if they're part of the protocol spec.

modelcontextprotocol/specification#142

You are right, I should've suggested there instead sorry about that and thanks for the link