Skip to main content
Glama

validation_check

DestructiveIdempotent

Executes one frozen validation component against existing run evidence, enabling rechecks of old runs without rerunning simulations and returning a durable operation ID.

Instructions

Execute one frozen component on existing evidence. environment/numerics/outputs use run_id and collected data_root='runs/<run_id>'; a terminal failed job can supply complete usable components. Matching old runs can be rechecked under revised criteria without another simulation. A component with checker_id additionally uses analysis_operation_id from analysis_submit on that run's collected data; program version, qualified fixtures and raw data are verified. Static/analysis checks use project files. Returns a durable operation id; missing evidence affects this component only.

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>",
      "revision": "<revision>",
      "plan_id": "<plan_id>",
      "component_id": "<component_id>",
      "op_id": "<op_id>"
    },
    "name": "validation_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
run_idNo
plan_idYes
task_idYes
revisionYes
data_rootNo
component_idYes
analysis_operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description gives no indication of what is written or destroyed, or what permissions/token are needed. What it does add beyond annotations is useful failure-isolation semantics ('missing evidence affects this component only') and the durable operation id, which is real value the annotations do not convey. Net: some added context over a mutation tool that still hides its side effects.

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?

Information density is high with little filler, but the text is a semicolon-chained block whose key routing rules are buried mid-paragraph rather than front-loaded. The 'checker_id' reference inside a component_id schema adds noise for the reader.

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 the return shape need not be explained, and the description does establish data prerequisites and partial-failure isolation. But for a destructive, idempotent, 9-parameter tool with 0% schema coverage, it omits the write semantics, token/auth expectations, and what plan_id and revision pin down.

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% across 9 parameters, so the description must carry the load, and it only explains run_id, data_root, and analysis_operation_id. Required parameters op_id, plan_id, task_id, revision, and component_id — plus the optional token — are left completely undefined, and the description even references 'checker_id', which is not a schema field, risking confusion with component_id.

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?

'Execute one frozen component on existing evidence' gives a concrete verb and resource, and the mention of analysis_operation_id/analysis_submit ties it to a distinct stage versus validation_plan or validation_compare. The phrase 'frozen component' is jargon that an agent must infer, so it stops short of a clean 5.

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

Usage Guidelines4/5

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

It states the conditional routing clearly: environment/numerics/outputs need run_id plus data_root, checker components additionally need analysis_operation_id from analysis_submit, and static/analysis checks use project files. It also explains a valuable re-use case (rechecking old runs under revised criteria without resimulating). It never names a sibling tool as an explicit alternative, so it is contextual rather than prescriptive.

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