a207-router-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_safety_gateA | 安全闸：P0 危急词扫描 + MX-1 分期互斥 / MX-2 游戏化隔离 / MX-3 写权收口。 返回 allow 为 false 时，调度 Agent 必须终止本次路由并按 reason 处置。 |
| classify_intentA | 意图路由：规则命中优先，返回目标 MCP、允许的 caller、槽位与置信度。 |
| check_permissionC | 权限矩阵执行点：caller x MCP x read/write，写工具按 MX-3 收口判定。 |
| extract_slotsC | 规则抽槽位：patient_id / food / analyte / date / number / 量具 / 时间窗。 |
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 4 tools
Tool purposes are mostly distinct, but check_permission and classify_intent both deal with caller permissions, and extract_slots overlaps with classify_intent's slot output, creating potential confusion about when to call each. Descriptions help clarify the different aspects (permission matrix vs routing vs safety gate vs slot extraction).
All tool names follow a consistent verb_noun pattern with lowercase snake_case: check_permission, check_safety_gate, extract_slots, classify_intent. Predictable and uniform.
With only 4 tools, the server is tightly focused on routing and safety. Each tool covers a distinct aspect of the routing pipeline without redundancy, making the count well-scoped.
The tool set covers the full routing lifecycle: intent classification, slot extraction, permission checking, and safety gating. No obvious missing operations for the stated router purpose; the safety gate includes comprehensive MX-1/MX-2/MX-3 rules.