Skip to main content
Glama

validation_match

Read-onlyIdempotent

Compares task inputs, conditions, environment, and measurements with a snapshot and plan to return direct, partial, or needs_validation plus exact missing components, without running simulations.

Instructions

Compare actual input dependencies, conditions, environment and current measurements. Returns direct/partial/needs_validation with exact missing components. Matching does not run a simulation.

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>",
      "snapshot_id": "<snapshot_id>",
      "plan_id": "<plan_id>"
    },
    "name": "validation_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes
task_idYes
snapshot_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description usefully adds the output vocabulary — direct/partial/needs_validation plus exact missing components — and explicitly says no simulation is executed. That is meaningful context beyond the annotations, though it omits how missing components are reported.

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?

Two sentences, front-loaded, with no filler; the negative constraint is placed last where it belongs. The first sentence, however, is a dense list of nouns that reads tersely without clarifying the comparison target.

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?

An output schema exists, so return values need not be re-explained, but for a tool requiring three opaque IDs the description supplies none of the semantics needed to invoke it correctly. The absence of parameter meaning leaves a critical gap that neither schema nor annotations fill.

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% and all three parameters (task_id, snapshot_id, plan_id) are required but completely undocumented. The description never mentions them or explains which one anchors the match, so an agent cannot tell what to pass or what their relationships are.

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 the objects (input dependencies, conditions, environment, measurements) are stated, and the return categories (direct/partial/needs_validation) hint at a verdict tool. But the description never says what the comparison is against — presumably the plan/snapshot referenced by the required IDs — so the core purpose stays fuzzy and is not distinguished from siblings like validation_check or validation_compare.

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

Usage Guidelines2/5

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

The only guidance is the exclusion "Matching does not run a simulation," which rules out one behavior but gives no when-to-use condition and no routing to any alternative among the many validation_* siblings. An agent has to guess whether to call this, validation_check, or validation_compare.

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