pr-guard-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 |
|---|---|
| analyze_pr_diffD | – |
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 1 tool
With only one tool, there is no possibility of overlap or confusion between tools. The lone tool is inherently distinct.
A single tool name trivially follows a consistent pattern. The verb_noun structure (analyze_pr_diff) is clear and conventional.
A single tool is too few for a server meant to guard pull requests. This feels extremely thin and likely insufficient for real-world use.
The server exposes only one operation with no description, making it impossible to assess coverage. There is no evidence of a complete lifecycle or workflow, and agents cannot perform any related actions beyond this single vague analysis.