Skip to main content
Glama

checker_register

DestructiveIdempotent

Registers a native checker by freezing its script hash, fixtures, expected results, and criteria, and requires all positive and negative test cases to match.

Instructions

Qualify a native checker after analysis_submit ran independent positive and negative fixtures. cases: [{operation_id,output,expected_passed}]. criteria is one JSON values/bounds check; its path is supplied from each actual output. Freeze script hash, fixtures, expected results and criteria; all cases must match.

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>",
      "name": "<name>",
      "cases": "<cases>",
      "criteria": "<criteria>",
      "op_id": "<op_id>"
    },
    "name": "checker_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
casesYes
op_idYes
tokenNo
task_idYes
criteriaYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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, so the mutation/profile is known. The description adds real value beyond that by stating the freeze semantics (hash, fixtures, expected results, criteria are pinned) and the hard constraint that 'all cases must match'. It still omits whether re-registration overwrites a prior checker, what happens on a mismatch, and any auth implication of the token parameter.

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 action is front-loaded and the text is dense with no filler, which is good for a technical audience. But the telegraphic phrasing ('Qualify', 'its path is supplied from each actual output') is ambiguous enough that an agent must re-read to parse the criteria semantics, so compactness costs clarity.

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 explained, and the description does convey the essential registration semantics and the all-cases-must-match gate. For a destructive, 7-parameter mutation with zero schema descriptions, though, the missing meaning for five parameters and the unstated overwrite/failure behavior leave gaps.

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 7 parameters, so the description must carry the burden and it only partially does. It documents the shape of cases ([{operation_id,output,expected_passed}]) and the meaning of criteria (a JSON values/bounds check whose path comes from each actual output), but task_id, revision, name, op_id and token receive no explanation at all.

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 names a specific action and object ('Qualify a native checker') and then clarifies the concrete effect ('Freeze script hash, fixtures, expected results and criteria'), so the agent can tell this is a registration/snapshot operation rather than a check execution. It does not differentiate itself from siblings such as checker_check, so it stops short of a 5.

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?

A precondition is given explicitly ('after analysis_submit ran independent positive and negative fixtures'), which tells the agent when this tool becomes applicable. However, there is no statement of when not to use it, no mention of what to do if fixtures do not yet exist, and no routing against sibling tools like checker_check or check_run.

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