Skip to main content
Glama

arobi_verify_chain

Locally recompute sealed records to verify SHA-256 hash chain and Ed25519 signatures, reporting the first broken record and reason if tampering is detected.

Instructions

Recompute a set of sealed records locally and report whether the SHA-256 hash chain and Ed25519 signatures are intact, pinpointing the first broken record index and reason if tampered.

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": {
      "records": "<records>"
    },
    "name": "arobi_verify_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYesOrdered array of sealed records returned by arobi_route_grant, arobi_authorize, or arobi_classify_and_route.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the load and does well: it discloses that verification is local recomputation, names the exact primitives (SHA-256 chain, Ed25519 signatures), and specifies the failure output (first broken index plus reason) rather than just 'returns true/false'. It does not state whether malformed or unsigned input is rejected or reported, and leaves purity/read-only status implicit.

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?

One sentence, front-loaded with the action, followed by the outcome and the failure detail. Nothing is padded and no clause is redundant.

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

Completeness4/5

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

For a single-parameter verification tool with no output schema and no annotations, the description covers what is checked, how, and what a failure looks like. Only the success-case return shape and handling of invalid input remain unstated, which are minor gaps.

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 coverage is 100% for the single 'records' parameter, so the schema already defines it as an ordered array from the named sibling tools. The description reinforces that these are sealed records and, via 'first broken record index', implies ordering matters, but adds no syntax or format detail beyond that.

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 pairs a specific verb (recompute/verify) with a specific resource (sealed records) and states exactly what the tool reports: hash-chain and signature integrity plus the first broken index and reason. That framing also implicitly separates it from the sibling tools that produce sealed records in the first place.

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?

Usage is only implied: the schema note that records come from arobi_route_grant, arobi_authorize, or arobi_classify_and_route makes the workflow (produce, then verify) inferable, and 'locally' hints at when this is preferable. There is no explicit statement of when to call it versus alternatives or what to do when verification fails.

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