Skip to main content
Glama

Arobi Immaculate MCP

arobi_verify_chain

Recompute a set of sealed spine records and report whether the hash chain is continuous, which record breaks it, and why. Verification only — it re-derives, it does not re-execute.

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
recordsYesSealed records in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 burden itself and does disclose the most important behavioral trait: it is a pure re-derivation with no re-execution or side effects. It also describes the shape of the result (continuous or not, which record breaks, and why). It is silent on edge cases such as unsealed or out-of-order input and on cost/latency for large record sets.

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?

Two short sentences, front-loaded with the action and result, followed by the scope constraint. No filler or restatement of the tool name.

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 one-parameter tool with no output schema, the description effectively conveys what is returned (continuity verdict, breaking record, cause), which is the main risk. Some behavior around invalid or unsealed input is left unstated, keeping it just short of fully complete.

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 100% and the single parameter is already documented as 'Sealed records in order.' The description reinforces that the records are sealed spine records in sequence but adds no format, size, or validation detail beyond what the schema states, so the baseline of 3 applies.

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 (recompute/verify) and a specific resource (sealed spine records / hash chain), and immediately names what it reports: continuity, the breaking record, and the reason. The closing clause 'it re-derives, it does not re-execute' explicitly separates it from a re-run/execution behavior, so an agent can distinguish its role without opening the schema.

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?

The exclusion 'Verification only — it re-derives, it does not re-execute' tells the agent when this tool is not appropriate, which is the key usage boundary. It does not name an alternative tool or state prerequisites (e.g., records must already be sealed), so it falls short of a full when/when-not/alternatives statement.

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.