tracewise-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_requirementC | A requirement (use-case flow, e.g. UC10S1) with the other flows of its use case. |
| search_codeB | Find classes by what they do. Returns class names, packages and purposes. |
| read_classC | A class's package, comment and method signatures. |
| related_classesC | Project classes a class uses and the classes that use it, from the call graph. |
| propose_linkA | Propose that a class implements a requirement. It goes to the review queue, not the trace matrix. |
| trace_matrixC | Reviewed and accepted links: requirement id -> classes. |
| coverage_gapsC | Requirements with no accepted link yet. |
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 targets a clearly distinct operation: requirement lookup, code search, class reading, related-class traversal, link proposal, accepted trace inspection, and gap detection. The boundary between proposed links and accepted trace-matrix links is especially clear.
All names use consistent snake_case and are readable. Some are verb-led (get_requirement, search_code, read_class, propose_link) while others are noun phrases (trace_matrix, coverage_gaps), which is a minor deviation from a strict verb_noun pattern.
Seven tools is well-scoped for a traceability-focused server. Each tool covers a meaningful part of the workflow without obvious redundancy.
The surface covers requirement lookup, code exploration, link proposal, trace inspection, and gap analysis. However, there is no way to list or search requirements, and proposed links go to a review queue with no tool to inspect or accept/reject them, leaving notable lifecycle gaps.