Skip to main content
Glama

review

Verify recorded run checksums offline and recompute metrics from a run ID, directory, or record.json file.

Instructions

Offline checksum verification and metric recomputation from run ID, directory or record.json.

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": {
      "record": "<record>"
    },
    "name": "review"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the operation is offline and involves checksum verification and metric recomputation, but does not state whether it only reads data, writes or persists results, requires authentication, or how failures 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler. The core purpose and input sources are stated immediately, making it easy to scan.

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?

For a tool with one unexplained parameter, no annotations, no output schema, and no documented return behavior, the description is too thin. It does not explain what the verification or recomputation produces, nor does it resolve the ambiguous accepted forms for the 'record' parameter.

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

Parameters3/5

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

The schema only defines a required 'record' string with 0% description coverage. The description partially compensates by saying it can accept a run ID, directory, or record.json, but it does not clarify the expected format or how the parameter name 'record' maps to those accepted inputs.

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 action: offline checksum verification and metric recomputation. It identifies acceptable input sources (run ID, directory, or record.json), which helps an agent understand the tool’s purpose despite the vague name 'review'.

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?

It mentions 'Offline' as a context clue but gives no explicit when-to-use guidance or alternatives. It does not say whether to use this instead of get_run, compare, or describe, nor does it state prerequisites or when-not-to-use conditions.

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