Skip to main content
Glama

hands_verify_trail

Read-onlyIdempotent

Verifies the tamper-evident SHA-256 hash chain of a Ghost Hands trail. Returns ok=true only if every link checks out; otherwise names the first broken event.

Instructions

Verify the tamper-evident hash chain of a Ghost Hands trail (v1.0+): returns ok=true only if every event's SHA-256 chain link checks out, with the first broken event named when it does not. Pass 'events' (a trail as returned by hands_trail) or omit it to verify this session's own trail. A trail written before hash chaining is reported as legacy, never passed. Read-only; nothing is executed.

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": "hands_verify_trail"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsNoTrail events to verify. Omit to verify this session's trail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds real behavioral detail: the exact pass condition (every SHA-256 link checks out), failure reporting (first broken event named), and the edge case that pre-chaining trails are reported as legacy and never passed. It also explicitly reassures that nothing is executed.

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 tight sentences, front-loaded with what is verified and what the result means, then the parameter choice, then the legacy caveat. No redundant or filler wording.

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 no output schema, the description carries the return-value burden and does so: it explains the ok flag, the named first broken event, and the legacy outcome. For a single-optional-parameter read-only tool, nothing needed to call it correctly 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by identifying the expected provenance of 'events' (a trail as returned by hands_trail) and reinforcing the omit-to-use-session-trail behavior. That provenance link is genuinely useful for constructing a valid call.

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 and resource ('Verify the tamper-evident hash chain of a Ghost Hands trail') plus version scope (v1.0+), and specifies the success/failure semantics (ok=true, first broken event named). An agent can distinguish this from hands_trail, which produces the trail this tool consumes.

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?

Gives clear selection logic for the single parameter: pass 'events' from hands_trail, or omit it to verify this session's own trail. It does not spell out when verification is unnecessary or what to do on failure, but the invocation context is unambiguous.

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