Check whether an MCP server's tool definitions have changed since it was last trusted (rug-pull / schema-drift detection, the CVE-2025-54136 class). Returns how long the tool surface has been stable, how many times it has changed, and the last change. Use after approval to detect post-trust mutation.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The MCP server endpoint URL to check. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses what the tool returns (stability duration, change count, last change) and frames it as a safety check. It does not detail network behavior or error handling, but the core behavioral trait is well communicated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary purpose, and wastes no words. Every sentence adds value: purpose, what is returned, and when to use.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one parameter (100% coverage) and no output schema, the description adequately explains the return values. It covers purpose, usage, and result structure. It could mention prerequisites or error conditions, but it is fairly complete for a simple check tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description repeats the schema's parameter description ('The MCP server endpoint URL to check') without adding new meaning. No additional detail on format or constraints is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('check') and resource ('an MCP server's tool definitions'), clearly indicating the tool's purpose. It also references a known vulnerability class (CVE-2025-54136) to differentiate from sibling tools like grade_mcp_server or verify_before_execute.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use: 'Use after approval to detect post-trust mutation.' This provides clear context for invocation. It does not explicitly mention when not to use or name alternatives, but the guidance is sufficient for most agents.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct concern: drift detection, grading, and pre-execution verification. Descriptions clearly differentiate their purposes with no overlap.
Tools use consistent snake_case with verb_noun pattern (check_drift, grade_server), though 'verify_before_execute' uses a slightly longer verb_prep_noun form. Overall pattern is clear and predictable.
Three tools is ideal for this focused server—each has a clear role without unnecessary complexity or missing essentials.
Covers the core trust verification workflow: drift detection, grading, and pre-execution gating. Minor gaps like a reset or history tool could exist but are not essential for primary use.
