workflow-guard-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| guard_checkB | Evaluate a proposed coding-agent action. Advisory unless the host wires the result into enforcement. |
| guard_statusA | Report guard capabilities and the enforcement boundary. |
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 2 tools
guard_check and guard_status have clearly distinct purposes: one evaluates an action, the other reports capabilities and enforcement boundaries. There is no overlap or ambiguity between them.
Both tools follow a consistent guard_ prefix with lowercase underscore naming. The pattern is uniform and predictable.
With only 2 tools, the server feels thin even for its narrow purpose. The count is borderline, sitting at the low end of what might be considered a minimal but workable surface.
The two tools cover the core guard workflow (evaluate action, check status) with only minor gaps like listing specific rules or explaining decisions. Agents can likely work around these by using the provided tools.