Router-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMBEDDING_HOST | No | 监听地址 | |
| EMBEDDING_PORT | No | 监听端口 | |
| EMBEDDING_DEVICE | No | 强制设备，例如 `cpu`、`mps`、`cuda` | |
| EMBEDDING_MODEL_NAME | No | 自定义本地模型名称 |
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 |
|---|---|
| route_queryD | – |
| clarify_queryD | – |
| validate_routeD | – |
| list_capabilitiesD | – |
| explain_routeD | – |
| plan_taskD | – |
| validate_capabilitiesD | – |
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 7 tools
Most tools have distinct purposes: clarify_query, explain_route, route_query, and validate_route target different stages of query processing, while list_capabilities and validate_capabilities focus on server capabilities. However, plan_task is somewhat vague and could overlap with route_query or clarify_query in function.
All tool names follow a consistent verb_noun pattern using snake_case, such as clarify_query, explain_route, and list_capabilities. There are no deviations in naming conventions, making the set predictable and readable.
With 7 tools, the count is well-scoped for a router server, covering query clarification, routing, validation, and capability management without being overwhelming. Each tool appears to serve a specific role in the routing workflow.
The tool set covers key aspects of routing: query clarification, route explanation, planning, routing, and validation, along with capability listing and validation. A minor gap might be the lack of tools for dynamic route updates or error handling, but core operations are present.