lazy-mcp-router
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_backendsA | List lazy MCP router runtime backends without starting them. |
| search_toolsA | Search declared and loaded router tools without starting cold backends. |
| load_toolC | Load the backend that owns a tool and return its safe tool detail. |
| call_toolC | Call a router tool through lazy lifecycle, policy, timeout, and audit gates. |
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
Each tool has a distinct role: listing backends, searching tools, loading a specific tool, and invoking a tool. No overlap in purpose, and the descriptions clearly differentiate the lifecycle stages.
All tool names follow the verb_noun pattern in snake_case: list_backends, search_tools, load_tool, call_tool. The naming is uniform and predictable.
Four tools is a focused, well-scoped set for a router server. Each tool serves a necessary part of the workflow without redundancy or bloat.
The core router lifecycle is covered: inspect, search, load, and call. A minor gap is the lack of an explicit unload or backend status operation, but the essential functionality is complete.