GuardRails-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GUARDRAILS_DATA_DIR | No | Override the default `.guardrails` data directory to share an absolute directory across CLI, MCP, and dashboard. | .guardrails |
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 |
|---|---|
| list_casesA | List the six fictional, labeled cases and evaluation limitations. |
| run_demoA | Run seeded fixtures with zero API calls; persist a local run. This is not model performance. |
| list_runsA | List up to 30 local runs; running records can be stale after a hard crash. |
| get_runA | Read one local run, including checks, outputs, provenance, and known limitations. |
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 targets a distinct resource and action: list_cases covers fixed cases, run_demo creates a run, list_runs lists existing runs, and get_run retrieves a specific run. There is no overlap or ambiguity in selecting the right tool.
All tool names use snake_case and follow a verb_noun pattern: list_cases, run_demo, list_runs, get_run. The convention is consistent and predictable throughout.
Four tools are well-scoped for a focused evaluation/demo server. Each tool earns its place by covering a core operation without redundancy or bloat.
The surface covers the essential lifecycle: listing cases, running a demo, and inspecting runs. Minor gaps exist, such as no way to delete or clean up runs and no individual case retrieval, but these are likely workarounds for the stated demo purpose.