spec-guard
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 |
|---|---|
| spec_check_interfacesD | – |
| spec_check_modelsD | – |
| spec_check_securityD | – |
| spec_check_envD | – |
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
Tool names specify distinct aspects (env, interfaces, models, security), so agents can differentiate them. Without descriptions, there is slight ambiguity about exact scope, but the naming is clear enough.
All tools follow a consistent 'spec_check_<aspect>' pattern, making them predictable and easy to understand.
Four tools is a reasonable scope for a specialized specification checker. It is neither too few nor too many for the domain.
The set covers key specification areas (env, interfaces, models, security), but lacks a composite check or a tool for performing all checks at once, which is a minor gap.