mcp-timeout-demo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TIMEOUT_DEMO_CONFIG | No | Path to a JSON configuration file with per-tool timeout overrides. The file should have shape { 'tools': { 'long_running_task': { 'timeout_ms': 60000 } } }. Missing file is an error. | |
| MCP_TIMEOUT_DEMO_TIMEOUT_MS__LONG_RUNNING_TASK | No | Default timeout in milliseconds for the long_running_task tool. Overrides the built-in default of 5000 ms. Takes precedence over the JSON config file. | 5000 |
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 |
|---|---|
| long_running_taskD | – |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap. Every available tool has a distinct purpose by virtue of being the sole tool.
With a single tool, naming consistency is trivially satisfied. The name 'long_running_task' is clear and follows a descriptive pattern, although no pattern can be established from one example.
A single tool feels thin for general use, but it is borderline acceptable for a server explicitly named 'mcp-timeout-demo' whose purpose appears to be demonstrating timeout behavior. One tool may be intentionally minimal for this narrow scope.
For a server dedicated to timeout demonstration, the 'long_running_task' tool fully covers the apparent purpose. There are no obvious gaps or dead ends given the focused domain.