Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Verify the chain against an external anchor

chain_verify_anchored
Read-onlyIdempotent

Verifies the tenant journal chain and confirms it extends a supplied external anchor, proving history below the anchor was not rewritten.

Instructions

Verify the caller's tenant journal chain (exactly as chain_verify) and additionally that the chain extends an externally held anchor: the receipt at the anchor sequence must carry the anchor hash, proving history was not rewritten below the anchor. Caller must be a principal of class tenant_owner, issuer, support_reader, or auditor. Use chain_verify when no external anchor exists. Read-only.

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": {
      "anchor_hash": "<anchor_hash>",
      "_tenant_id": "<_tenant_id>",
      "_principal_id": "<_principal_id>"
    },
    "name": "chain_verify_anchored"
  }
}

Input Schema

NameRequiredDescriptionDefault
_tenant_idYesTenant the call acts for. The tenant must exist; an unknown tenant is refused with state LICENSE_UNKNOWN. Transport authentication is a deployment concern -- this parameter scopes the call, it does not authenticate it.
anchor_hashYesExternally witnessed journal hash to anchor against (required).
_principal_idYesActing principal inside the tenant. Principal-gated tools refuse unknown principals and principals of the wrong class; executions (tier T2) additionally require a live, unexpired mandate covering the product and the operation class.
anchor_sequenceNoOptional sequence number the anchor hash belongs to.

Output Schema

NameRequiredDescriptionDefault
okNo
countNo
reasonNo
failed_atNo
head_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds genuine context beyond that by naming the eligible principal classes and explaining the proof mechanism (the receipt at the anchor sequence must carry the anchor hash, proving history was not rewritten below it). It does not discuss failure states or response shape, but the output schema covers returns, so the remaining gap is small.

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 key differentiator and the ownership/anchor requirement are front-loaded in the first sentence, the authorization constraint and the alternate-tool routing follow, and it closes with a one-word safety restatement. There is no filler and nothing is buried.

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?

For a 4-parameter, mostly-required verification tool with full schema descriptions and an output schema, the description supplies everything an agent needs: what is verified, how the anchor proof works, who may call it, and which sibling to use instead. No material aspect is left to inference.

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 baseline is 3. The description earns a bump because it explains the semantic relationship between the two anchor parameters — that anchor_sequence identifies the receipt which must carry anchor_hash — which is more than the schema's per-field strings convey in isolation.

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 names a specific verb (verify) and resource (the caller's tenant journal chain) and immediately scopes the extra work: it also proves the chain extends an externally held anchor whose hash must appear in the receipt at the anchor sequence. It explicitly differentiates itself from the sibling chain_verify by describing itself as that check 'plus' the anchor proof.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: 'Use chain_verify when no external anchor exists,' which tells the agent exactly when to prefer the sibling. It also states the principal classes permitted to call it, so both the selection decision and the call precondition are covered.

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