Skip to main content
Glama

checker_check

DestructiveIdempotent

Validates a completed analysis against a qualified program's fixed criteria and exact script version, then queues a service receipt for the measured output and companion artifacts.

Instructions

Check a completed analysis using a qualified program's fixed criteria and exact script version. Queue a service receipt for the measured output and companion artifacts.

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>",
      "checker_id": "<checker_id>",
      "operation_id": "<operation_id>",
      "output": "<output>",
      "op_id": "<op_id>"
    },
    "name": "checker_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
outputYes
task_idYes
revisionYes
artifactsNo
checker_idYes
operation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false. The description adds that it queues a service receipt and involves companion artifacts, which is useful side-effect context beyond the annotations. However, it does not clarify what the destructive aspect affects, whether prior receipts are overwritten, or what authorization the token provides.

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?

The definition is two compact sentences with the core action front-loaded and no filler. The phrase 'service receipt' is somewhat opaque, but overall it is efficient and structurally clear.

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?

This is a destructive, idempotent mutation tool with eight parameters, six required, and no schema descriptions. While the output schema means return values need not be described, the definition is still too thin on parameter meanings, preconditions, and the consequences of the destructive hint. An agent would struggle to call it correctly from the description alone.

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%, so the description must carry the burden for eight parameters. It hints at checker_id ('qualified program'), revision ('exact script version'), output, and artifacts, but leaves task_id, operation_id, op_id, and token unexplained. That is inadequate for a six-required-parameter mutation tool.

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 states a specific verb and resource: 'Check a completed analysis,' and adds method details ('qualified program's fixed criteria and exact script version'). It also mentions the side effect of queuing a service receipt for the measured output and companion artifacts. It does not differentiate from siblings such as check_run, validation_check, or completion_check.

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 usage cue is 'completed analysis,' which implies this applies after an analysis finishes, but there is no explicit when-to-use guidance. It never names alternatives or explains when to choose this over check_run, validation_check, or checker_register. Prerequisites and when-not conditions are absent.

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