Skip to main content
Glama
ReportProof MCP Server

ReportProof MCP Server

by vikyathhj-ui

verify_report

Checks a draft report against a previously computed metrics object, flagging mismatched numbers and returning pass/fail results with discrepancies.

Instructions

Verify a draft report against a metrics object previously returned by compute_metrics.

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": {
      "report": "<report>",
      "metrics": "<metrics>"
    },
    "name": "verify_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowNoExtra numbers allowed in the text, e.g. [30] for a 30-day window.
reportYes
metricsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It adds one genuinely useful behavioral constraint — the metrics object must originate from a prior compute_metrics call — but says nothing about whether verification is read-only, what it reports back, or how mismatches are surfaced.

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?

A single front-loaded sentence with no filler; the prerequisite relationship is placed where an agent will read it first. It is arguably too terse given the tool's complexity, but nothing in it is wasted.

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

Completeness2/5

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

For a tool with a nested object parameter, no output schema, and no annotations, the description leaves major gaps: what checks are performed, whether the report is modified, and what a result looks like. The provenance hint for metrics is not enough to call it complete.

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 description coverage is only 33%, with report and metrics undocumented in the schema. The description compensates for metrics by fixing its provenance (output of compute_metrics), but adds no meaning for report beyond its name, and the nested structure of metrics remains unexplained.

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?

The description gives a specific verb and resource ('Verify a draft report') plus the object it is checked against, so the operation is immediately identifiable. It implicitly contrasts with compute_metrics by naming it as the upstream producer, but it does not distinguish itself from the sibling check_report.

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?

Usage is implied rather than stated: the phrase 'previously returned by compute_metrics' tells an agent this must follow a compute_metrics call. There is no explicit when-not guidance and no mention of when check_report would be the better choice.

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

Deploy Server

Other Tools