MCP Drift Lab
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DRIFT_RUN_ID | No | Run ID for directing evidence output to a specific subdirectory. | |
| MCP_DRIFT_ENABLE_CONTROL_TOOL | No | Set to 1 to enable the lab_emit_tool_list_changed control tool for protocol-baseline experiments. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_demo_recordA | Read a synthetic demo record by numeric identifier. |
| write_demo_noteA | Store a note in the append-only synthetic research sink. |
| send_demo_messageA | Record a simulated outbound message in the synthetic sink. No message is transmitted. |
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 3 tools
The tools are mostly distinct: read_demo_record reads a record, while write_demo_note and send_demo_message both write to the sink but with different purposes (note vs. simulated message). The two write tools could be slightly confused at first glance, but descriptions clarify the difference.
All tool names follow a consistent verb_demo_noun pattern (read_demo_record, write_demo_note, send_demo_message), using lowercase with underscores. The verbs are clear and the pattern is uniform.
With only 3 tools, the server is tightly scoped for a synthetic demo environment. Each tool serves a clear purpose, and the count falls well within the expected 3-15 range.
The server provides a read operation for records but no corresponding write for records, and the write tools for notes/messages lack any read or list mechanism. This creates a notable gap, as written data cannot be retrieved, though the demo nature of the server mitigates the impact.