Skip to main content
Glama

SCRIPTMASTERLABS — Calibration Court

Verify Ledger Hash Chain

court_verify_ledger
Read-only

Independently recompute the ledger's SHA-256 hash chain from genesis and cross-check the derived tables against it, returning the verification result together with the current head hash. Free. Use it to confirm that recorded predictions and outcomes have not been altered after the fact.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "court_verify_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description is fully consistent with that, framing the operation as an independent read-only recomputation. It adds real context beyond the annotations: the verification method (hash chain from genesis), what is returned (result and current head hash), and that the call is free. It does not discuss cost of a large ledger or failure modes, so not a 5.

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?

Three short sentences, front-loaded with the mechanism, followed by return value, cost, and the use case. Every sentence adds distinct information and there is no filler.

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?

With zero parameters, no output schema, and only a readOnly annotation, the description must carry return-value meaning, and it does: verification result plus current head hash. Nothing an agent needs in order to decide to call this and interpret the result is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain beyond confirming that no inputs are needed. Baseline 4 applies, and the description implies a whole-ledger scope rather than a targeted one, which is the right clarification to make.

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?

States a specific verb+resource: recompute the ledger's SHA-256 hash chain from genesis and cross-check derived tables. It also names the outputs (verification result plus head hash), which is more specific than any sibling name suggests, and clearly separates it from court_calibrate_labels, court_leaderboard, court_model_report, and court_recalibrate.

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?

"Use it to confirm that recorded predictions and outcomes have not been altered after the fact" gives a clear when-to-use condition. It does not name a when-not case or a competing alternative, but with no siblings doing verification this is a minor gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources