release-evidence-pack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELEASE_EVIDENCE_ALLOWED_ROOTS | No | One or more repository roots allowed for the server. Separate paths with ';' on Windows or ':' on Linux/macOS. If absent, only the current directory is allowed. |
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 |
|---|---|
| inspect_release_changesA | Inspect a local Git diff and classify release risk without changing the repository. |
| summarize_test_reportsA | Summarize local JUnit XML reports without returning testcase logs or captured output. |
| build_release_evidence_packA | Combine Git changes and JUnit reports into a risk decision, findings, and rollback checklist. |
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 3 tools
Each tool has a clearly distinct responsibility: one inspects Git changes, one summarizes test reports, one combines them into a final pack. No overlap or ambiguity in purpose.
All tool names follow a consistent verb_noun snake_case pattern (inspect_release_changes, summarize_test_reports, build_release_evidence_pack), making the set predictable and easy to navigate.
Three tools is well-scoped for the server's specific purpose of generating a release evidence pack. Each tool earns its place and there is no redundancy or bloat.
The tool set covers the entire workflow from inspecting changes and summarizing reports to building the final evidence pack. There are no obvious gaps or dead ends for the stated domain.