Skip to main content
Glama

mcpsense_verify

Read-only

Compares two saved JSON coverage reports using identical verification logic to identify before-and-after differences.

Instructions

Compare two saved JSON reports from equivalent completed coverage using the same verification logic as mcpsense verify.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "mcpsense_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYesAfter report path.
beforeYesBefore report path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful context by asserting the comparison uses the same verification logic as mcpsense verify, but says nothing about what a comparison yields (verdict, diff, regressions) or how mismatched reports are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, and the key constraint (equivalent completed coverage) is stated before the implementation note. Slightly dense but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only two-parameter tool this covers the inputs adequately, but with no output schema the description should say what the comparison returns and what counts as a failure. That return-value gap is the main missing piece for an agent to interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are already documented as before/after report paths, so the description's 'two saved JSON reports' merely restates the schema. It does not specify ordering semantics or the format/version expectations for the files beyond the coverage equivalence note; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compare') and resource ('two saved JSON reports') plus a qualifier ('from equivalent completed coverage'), which is enough to separate it from the scan/checks/discover siblings. It stops short of explicitly naming those siblings or contrasting with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'from equivalent completed coverage' implies a precondition for valid use, but the description never states when an agent should pick this tool over the sibling scan/checks tools, nor what to do if the reports differ in scope. Usage is inferred rather than guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.