starter-doc-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 |
|---|---|
| generate_full_blueprintC | Generates the entire synchronized, anti-hallucination engineering blueprint suite (PRD, SRS, ERD, SDD, DESIGN, Traceability Matrix, and Agent Instructions) as production-grade Markdown files. |
| generate_prdC | Generates an anti-hallucination Product Requirements Document (PRD.md) with MoSCoW prioritization, strict in-scope/out-of-scope boundaries, and BDD Gherkin acceptance criteria. |
| generate_srsC | Generates an ISO/IEC/IEEE 29148 compliant Software Requirements Specification (SRS.md) with strict functional inputs/outputs, error conditions, latency SLAs, and OWASP security constraints. |
| generate_erdB | Generates an Entity Relationship Diagram (ERD.md) with valid Mermaid diagram, complete data dictionary, index strategies, foreign key cascade behaviors, and production SQL DDL migrations. |
| generate_sddC | Generates a Software Design Document (SDD.md) with C4 diagrams (Mermaid), exhaustive API contracts, sequence diagrams, and Architectural Decision Records (ADRs). |
| generate_design_specC | Generates a frontend UI/UX Design Specification (DESIGN.md) with 60-30-10 color tokens, typography scale, atomic component hierarchy, and deterministic 5-State screen matrices (Empty, Loading, Error, Partial, Populated), and anti-slop UI/copy rules for implementing agents. |
| audit_spec_completenessA | Audits a specification document or text against the strict Anti-Hallucination rubric: checks for ambiguous buzzwords, missing error status codes, lack of Gherkin criteria, missing 5-state UI matrices, and returns a 0-100 quality score with surgical fix advice. |
| list_blueprint_templatesA | Lists production-grade architecture presets available for rapid bootstrapping (SaaS B2B, E-Commerce, AI Agent Platform). |
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 8 tools
Each generate_* tool targets a distinct, named artifact (SRS, PRD, ERD, SDD, DESIGN), and audit_spec_completeness and list_blueprint_templates serve clearly different roles. The only overlap is generate_full_blueprint, which subsumes all five document generators, so an agent must decide between the bundle and an atomic document — a real but well-documented ambiguity.
All tools follow a consistent verb_noun snake_case pattern (generate_srs, generate_prd, audit_spec_completeness, list_blueprint_templates). The one longer name, generate_full_blueprint, still fits the same pattern without breaking convention.
Eight tools is well within the sweet spot for a documentation-generation server, with one generator per artifact plus a bundle, an auditor, and a template lister. Nothing feels padded or missing at the count level.
The surface covers the full spec suite (PRD, SRS, ERD, SDD, DESIGN) plus audit and template discovery, which is strong lifecycle coverage for the stated purpose. Minor gaps: Traceability Matrix and Agent Instructions are only reachable via the full blueprint bundle, and there is no tool to revise or patch an existing document after an audit.