spec-to-delivery
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 |
|---|---|
| parse_requirementsA | Extract identified requirements (REQ-001 style IDs) from a Markdown requirements document. Returns id, text, section, priority and line number for each. |
| diff_requirementsA | Compare two versions of a requirements document by requirement ID. Returns added, removed, changed (with before/after text) and unchanged IDs. |
| parse_scenariosA | Parse Gherkin feature text and return each scenario with the requirement IDs it is linked to (via @REQ-001 tags or IDs in the scenario title). |
| traceability_matrixC | Build a requirement-to-scenario traceability matrix. Returns per-requirement coverage, uncovered requirement IDs, orphan scenarios, unknown IDs, a coverage percentage, and a ready-to-paste Markdown table. |
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 distinct purpose: parsing requirements, diffing requirements, parsing scenarios, and building a traceability matrix. There is no overlap or ambiguity; an agent can easily select the correct tool for a specific task.
The first three tools follow a consistent verb_noun pattern (parse_requirements, diff_requirements, parse_scenarios), but traceability_matrix is a noun phrase rather than a verb_action. This minor deviation is easily readable but slightly inconsistent.
Four tools is well within the ideal range and each tool covers a distinct stage of the requirements-to-scenario workflow. The scope is focused and every tool earns its place.
The tool set covers parsing, diffing, scenario extraction, and traceability, which forms a coherent core workflow. A minor gap is the lack of tools for updating or generating requirements, but this is not a severe omission for the stated purpose.