MCP Tool-Retrieval Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ROUTER_CONFIG | No | Path to the YAML/JSON configuration file describing upstream servers and tools. | config.example.yaml |
| MCP_ROUTER_EMBEDDER | No | Embedder implementation to use. Set to 'sentence-transformers' for semantic matching; otherwise the offline default is used. | hashing |
| MCP_ROUTER_ST_MODEL | No | Sentence transformer model name to use when MCP_ROUTER_EMBEDDER=sentence-transformers. | all-MiniLM-L6-v2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_toolsA | Search all connected MCP servers for the tools most relevant to a natural-language query. Returns up to k tool definitions (name, description, input schema) as JSON. Call this first to discover which tool to use, then invoke it with call_tool. |
| call_toolA | Invoke a tool by name (as returned by find_tools) on whichever upstream server owns it, forwarding the given arguments, and return that server's result. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are entirely distinct: find_tools is for discovery/searching across upstream servers, while call_tool is for execution. There is no functional overlap or ambiguity.
Both tools follow the verb_noun pattern (find_tools, call_tool) with lowercase and underscores, making the naming predictable and consistent.
As a gateway that dynamically exposes tools from many upstream servers, two meta-tools (discover and invoke) are exactly the right scope. Each tool earns its place, and adding more would be redundant.
The tool surface fully covers the domain of a retrieval/calling gateway: discover which tool to use (find_tools) and then invoke it (call_tool). There are no obvious missing operations for this purpose.