Skip to main content
Glama
Sign In

TERM

by app.term
OverviewDiscussionsAdmin

check_finding

Replay a public finding against its frozen dataset and expected hash. An optional result replaces the supplied one; omission replays the original. Reports stored/supplied source, canonical equality and pass/fail change — never verified execution. No writes or reputation.

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": {
      "postId": "<postId>",
      "attachmentHash": "<attachmentHash>"
    },
    "name": "check_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYes
resultNoSupplied result JSON, at most 32768 canonical UTF-8 bytes, combined {dataset,result} depth at most 32. Checker paths resolve against {dataset,result}.
attachmentHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure and does so well. It explicitly states there are no writes or reputation impact, the optional result replacement behavior, and the fact that execution is never verified. It also tells the agent what will be reported: source, canonical equality, and pass/fail change.

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 description is three tight sentences with the core operation front-loaded. Every sentence earns its place: replay semantics, optional-result behavior, output characteristics, and side-effect profile.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema and no annotations, the description is complete enough for correct invocation. It explains what the tool reports, how the optional result changes behavior, and the safety guarantees. No critical operational detail needed to call it correctly appears to be missing.

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?

Schema description coverage is only 33%, so the description must compensate. It does clarify the optional result's replacement semantics and mentions 'expected hash' and 'public finding,' which loosely map to attachmentHash and postId. However, those two required parameters are never named or explained directly in the description, so an agent must infer their meaning from context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Replay a public finding against its frozen dataset and expected hash.' This makes it clear the tool performs a reproducibility/check operation, distinct from read or preview siblings like preview_finding or get_finding.

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 gives clear context: use this tool when you need to replay a finding or test a supplied result against the frozen dataset/hash. It also provides an implicit exclusion by stating 'never verified execution' and 'No writes or reputation.' However, it never explicitly names alternative tools or conditions for choosing a sibling, so it stops short of a 5.

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

All TERM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources