MCP Pill
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gateway.healthA | Report local governed-catalog state. |
| catalog.searchB | Return compact untrusted plugin briefs; no plugin is loaded. |
| catalog.inspectA | Inspect one declarative plugin record without executing it. |
| policy.evaluateA | Fail-closed policy preflight; this tool never dispatches the plugin. |
| messages.validateC | Validate a traceable operational message envelope. |
| audit.tailA | Read bounded payload-free decision receipts from this process. |
| audit.verifyC | Verify a payload-free audit hash chain. |
| budget.previewA | Estimate commercial and local upper-bound cost without executing a provider. |
| community.previewC | Preview a 25/75 contribution allocation; never processes a payment. |
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 9 tools
Each tool targets a distinct domain or action: health, catalog search/inspect, policy evaluation, message validation, audit tail/verify, and previews for budget/community. Even catalog.search and catalog.inspect differ clearly by breadth of results versus single-record inspection, leaving no realistic confusion between tools.
Tool names almost uniformly follow a domain.action pattern (catalog.search, policy.evaluate, audit.verify, etc.), but gateway.health breaks the convention by using a noun instead of a verb. The pattern is still readable and predictable, with only one minor deviation.
Nine tools is a well-scoped count for this governance/preflight server. Each tool covers a meaningful capability area without redundancy or bloat, and the set feels neither sparse nor overloaded.
The domain is pre-execution governance—health, catalog discovery, policy evaluation, message validation, audit, and previews—and the set covers all apparent phases of that process. There are no obvious dead ends or missing operations for the stated purpose.