DocGuard
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docguard_guardA | Run every enabled DocGuard validator against the project's canonical docs. Returns the full guard JSON contract: status (PASS/WARN/FAIL), structured findings with stable codes and suggestions, nextStep, doc coverage map, semantic-claim count, and per-validator results. |
| docguard_scoreA | Compute the project's CDD maturity score (0-100) with letter grade and per-category breakdown. |
| docguard_explainA | Explain a stable DocGuard finding code (e.g. STR001, ENV003): what it means, which validator emits it, and the inline suppression to use if it's a confirmed false positive. |
| docguard_verify_evidenceA | Evaluate |
| docguard_verify_claimsA | Extract the semantic claims in the project's canonical docs — documented numbers, limits, and enums — as a verification task list. Deterministic discovery, LLM judgment — the caller verifies each claim against the code. |
| docguard_reportA | Generate the commit-stamped compliance-evidence bundle: guard verdict per validator, findings grouped by stable code, CDD score, ALCOA+ data-integrity attributes, fix history, and a tamper-evident sha256 integrity hash. Evidence, not a gate — it reports state without failing. |
| docguard_diagnoseA | Run guard and return only what needs fixing: failing/warning validators with their messages, structured findings, and suggested next actions — shaped for an agent to act on. |
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 7 tools
Each tool has a distinct output role—full guard run, actionable subset, explanation, report, score, evidence verification, and claim extraction. The only potential confusion is docguard_guard vs docguard_diagnose, but their descriptions clearly separate full JSON from fix-oriented results.
All tools share the docguard_ prefix and use clear action verbs, but the pattern is not fully uniform: some are bare verbs (diagnose, explain, report, score, guard) while others use verb_noun (verify_evidence, verify_claims). docguard_guard is also slightly redundant, though the set remains predictable and readable.
Seven tools is well-scoped for a documentation-compliance utility; each tool addresses a distinct stage of the guard/report/verify workflow. No tool feels redundant, and the count is neither thin nor bloated.
The set covers the full read-only lifecycle: running validators, prioritizing fixes, explaining codes, scoring, reporting, and verifying both evidence files and semantic claims. Minor gaps like a validator-listing or configuration tool are possible, but agents can work around them using the guard output and explain tool.