Skip to main content
Glama

validation_compare

Destructive

Compare candidate and final plans against the same inputs and actual receipts—without new physics—to verify agreement and retain contrary evidence.

Instructions

Compare candidate/final plans against the same inputs and actual receipts without new physics. Host agents may propose/check candidates concurrently, then select component criteria with a rationale in validation_plan(reuse_sources=[...]). Agreement is not measurement; preserve contrary evidence.

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": {
      "task_id": "<task_id>",
      "plan_ids": "<plan_ids>",
      "snapshot_id": "<snapshot_id>"
    },
    "name": "validation_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
plan_idsYes
snapshot_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description never says what this tool writes or overwrites. A 'compare' tool that is marked destructive is exactly the case where the description must explain the side effects, and instead it only offers the caution 'preserve contrary evidence' and 'agreement is not measurement', which explain interpretation, not mutation.

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?

It is short (three sentences) and front-loads the purpose. But the middle sentence is a workflow digression into a different tool's parameter, and the closing aphorism costs space that could have documented the three required parameters or the destructive behavior.

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?

An output schema exists, so return values need not be described, which lightens the burden. Still, for a destructive three-parameter tool with zero schema description coverage, the definition omits both the parameters' meaning and the nature of the write, leaving real gaps for an agent to fill by guessing.

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

Parameters2/5

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

Schema description coverage is 0% for three required parameters (task_id, plan_ids, snapshot_id), so the description must compensate and does not: it never explains what a snapshot is, whether plan_ids can span tasks, or what 'same inputs' means relative to snapshot_id. The only parameter it names is reuse_sources, which belongs to validation_plan, not this tool.

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

Purpose3/5

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

The verb 'Compare' and object 'candidate/final plans' are stated, along with a scoping clause ('against the same inputs and actual receipts without new physics'). However, opaque phrasing like 'actual receipts' and 'without new physics' leaves an agent guessing at the actual comparison semantics, and it never clarifies how this differs from validation_match or validation_check.

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?

It implies a workflow ('host agents may propose/check candidates concurrently, then select component criteria with a rationale in validation_plan(reuse_sources=[...])'), which routes the agent to a sibling for a later step. But it never states when this tool should be called instead of validation_check or validation_match, nor what prerequisites (e.g., an existing snapshot) must be met.

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