Skip to main content
Glama

reports_compare

Read-onlyIdempotent

Compare exact report IDs to identify coverage differences, new findings, and unproven remediation states; optionally add source traces and portable input checks.

Instructions

Compare exact report IDs, retaining coverage differences and unproven remediation states. verification=true adds source traces and scope/build/assertion pairing; portable_inputs=true requires verification and only normalizes absolute targets for identical, complete canonical SHA256 source inputs with unchanged analysis scope. Binary and runtime bindings remain strict; disappearance never proves remediation. No source excerpts; bounded by max_bytes (4096-262144) with omitted counts.

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": "reports_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterYes
beforeYes
max_bytesNo
verificationNo
portable_inputsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / max_bytes
      Added value: +{
      +  "default": 65536,
      +  "title": "Max Bytes",
      +  "type": "integer"
      +}
  2. Changed2 schema fields changedv1.6.0
    • addedInput schema / properties / portable_inputs
      Added value: +{
      +  "default": false,
      +  "title": "Portable Inputs",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / verification
      Added value: +{
      +  "default": false,
      +  "title": "Verification",
      +  "type": "boolean"
      +}
  3. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description goes well beyond that: it discloses that no source excerpts are returned, that output is bounded by max_bytes with omitted counts, that binary and runtime bindings stay strict, and that disappearance never proves remediation. These are genuine semantic caveats an agent could not infer from the schema. The dense, jargon-laden phrasing ("scope/build/assertion pairing") blunts the value slightly.

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

Conciseness3/5

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

The purpose is front-loaded and every sentence carries technical content, so nothing is filler. However, the second and third sentences are long run-on clauses packed with unexplained terminology ("identical, complete canonical SHA256 source inputs with unchanged analysis scope"), which costs readability without shortening the text.

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

Completeness4/5

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

An output schema exists, so return-value structure need not be explained, and the description still covers the notable output constraints (no excerpts, byte bound, omitted counts). For a 5-parameter comparison tool with rich annotations, the remaining gap is the missing statement of what the required before/after inputs actually accept.

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

Parameters4/5

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

With 0% schema description coverage the description must carry the parameter burden, and it largely does: max_bytes is given an explicit range (4096-262144) and omission behavior, verification is described as adding source traces plus scope/build/assertion pairing, and portable_inputs is constrained as requiring verification and only normalizing absolute targets under identical canonical SHA256 inputs. It stops short of saying what format before/after strings must take beyond "report IDs".

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 opening clause gives a specific verb and resource ("Compare exact report IDs") and frames the scope as two named reports, which distinguishes it from reports_get and reports_history. What it does not do is state plainly that the two required string parameters are the report identifiers being compared, leaving that inference to the reader.

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 by the word "Compare" and by the conditional behavior of verification and portable_inputs, so an agent can guess this is the diff tool among the reports_* siblings. There is no explicit when-to-use guidance, no named alternative (e.g. use reports_get for a single report), and no statement of preconditions such as both reports needing to come from the same scan family.

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