MCP Failure Lab
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAB_DELAY_MS | No | Integer 0-10000 (default 1000). Delay in milliseconds used by the delay scenario before the tool response. | 1000 |
| LAB_FAILURES | No | Integer 0-10 (default 2). Number of initial failing calls used by the transient-error scenario. | 2 |
| LAB_SCENARIO | No | Injected fault behavior. One of: healthy (normal tool response), tool-error (valid result with isError=true), transient-error (first LAB_FAILURES calls fail), delay (wait LAB_DELAY_MS before tool response), malformed (valid JSON-RPC envelope, invalid text-block value), disconnect (exit during a tool response). Only the advertised lab_probe tool is affected. Configuration is read at process startup and scenarios reset per process. | healthy |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lab_probeC | Synthetic failure-lab probe. No external services, filesystem changes or credentials. |
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
There is only one tool, so there is no possibility of confusion or overlap. The single tool's purpose is clearly stated as a synthetic failure-lab probe.
With a single tool name (lab_probe), there is no inconsistency to assess. The snake_case naming is clear and readable.
A single trivial probe tool is an extreme mismatch for an MCP server, even one framed as a failure lab. There is no room for multiple probes, configuration, or lifecycle operations.
The apparent domain is a synthetic failure lab, which typically requires multiple probes, failure-mode selection, or reset capabilities. A single generic probe leaves significant gaps for any realistic lab use.