mcpgrade
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 |
|---|---|
| grade_mcp_serverA | Scores an MCP server on agent usability (A–F) and returns the specific defects that cost it points, each with a concrete fix. Grades description quality, schema design, tool naming, token cost and catalog consistency — the properties that determine whether a model picks the right tool and fills valid arguments, which spec-compliance checks do not measure. Returns a grade, per-category scores, finding counts by severity, and a prioritized finding list. Use this before depending on a third-party server, or after changing your own catalog. |
| explain_ruleA | Returns the full rationale for one grading rule: what it detects, why it degrades agent behaviour, and how to fix it. Use this after grade_mcp_server reports a finding you want to understand or dispute, rather than guessing what a rule ID means. |
| list_grading_rulesA | Lists every rule mcpgrade applies, with its identifier, severity and one-line summary. Use this to see what is checked before grading, or to find the identifier of a rule to pass to explain_rule. |
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 purpose: listing rules, explaining a rule, and grading a server. There is no overlap or potential for confusion between them.
All tool names follow a consistent verb_noun pattern: explain_rule, list_grading_rules, grade_mcp_server. The verbs are action-oriented and the objects are specific, making the names predictable and readable.
Three tools is well-scoped for this niche server. Each tool earns its place by covering the complete workflow of discovering, understanding, and applying grading rules.
The tool surface is complete for its stated purpose: list rules to discover them, explain rules to understand them, and grade a server to put them into action. There are no obvious gaps or dead ends.