standards-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 |
|---|---|
| list_standardsA | List every engineering standard in the library (id, title, and its section headings). Start here to see what rules exist before searching or fetching. |
| search_standardsA | Search the standards library with natural language and return the most relevant rule sections (which standard, which heading, and a snippet). Use this before answering any question about architecture, security, API, gRPC, compression, validation, options, messaging, UI/UX, or MCP policy — apply the rules found here rather than from memory. |
| get_standardA | Return a full engineering standard by id (e.g. '02'), slug ('02-architecture'), or name ('architecture'). Use after search to read the complete rules and checklist. |
| get_checklistA | Return the compliance checklist(s). Pass a standard id/name for one, or omit for every checklist across the library — use it as a Definition-of-Done gate before shipping. |
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 has a clearly distinct role: list for overview, search for targeted rule lookup, get_standard for full content, and get_checklist for compliance gates. There is no meaningful overlap between the tools.
All tool names follow a consistent verb_noun snake_case pattern: list_, search_, get_. The singular 'standard' vs plural 'standards' is a natural distinction between a single resource and the library as a whole.
Four tools is well-scoped for a read-only standards library. Each tool covers one distinct step in the workflow—discover, search, retrieve, and check compliance—without redundancy or bloat.
The surface is complete for its stated purpose: agents can list available standards, search relevant rules, fetch full standards, and obtain compliance checklists. No obvious gap exists for the intended read-only use case.