Skip to main content
Glama
Cyan Eclipse License Server

Cyan Eclipse License Server

Official

Show journal head and count

journal_info
Read-onlyIdempotent

Show a tenant’s journal head—receipt count, latest sequence, head hash, and genesis hash—to anchor or sanity-check the append-only hash chain before verifying it.

Instructions

Show the head of the caller's tenant journal: receipt count, latest sequence number, head hash, and genesis hash. The journal is the tenant's append-only, hash-chained record of every lifecycle operation and refusal. Caller must be a principal of class tenant_owner, issuer, support_reader, or auditor. Use it to anchor or sanity-check the chain; use chain_verify to recompute the whole chain and journal_list / receipt_get to read entries. 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": {
      "_tenant_id": "<_tenant_id>",
      "_principal_id": "<_principal_id>"
    },
    "name": "journal_info"
  }
}

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.
_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.

Output Schema

NameRequiredDescriptionDefault
countNo
sequenceNo
head_hashNo
tenant_idNo
genesis_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 the safety profile is carried; the description adds non-obvious context by explaining that the journal is an append-only hash-chained record of operations and refusals and by listing the principal classes permitted to call. The trailing "Read-only." merely restates the annotation and earns no extra credit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what is returned before the explanatory and routing clauses. The final "Read-only." is redundant given readOnlyHint and is the one piece of text that does not earn its place.

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?

An output schema exists, so return-field enumeration is a bonus rather than a necessity, and the description still names the key values. Authorization, chain semantics, and alternatives are all covered for what is otherwise a simple, zero-argument (aside from scoping) read tool.

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 both parameters are already documented; the description nonetheless adds meaning by framing _tenant_id as the tenant whose journal head is returned and by constraining _principal_id to specific classes (tenant_owner, issuer, support_reader, auditor). It does not add format or syntax detail beyond the schema.

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?

Uses a concrete verb ("Show") on a precisely defined resource ("the head of the caller's tenant journal") and enumerates exactly what is returned: receipt count, latest sequence number, head hash, genesis hash. An agent can distinguish it from journal_list, chain_verify and receipt_get without opening any schema.

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?

Explicitly states the intended use ("anchor or sanity-check the chain") and routes to named alternatives with their distinct purposes (chain_verify to recompute the whole chain, journal_list / receipt_get to read entries). It also states the authorization precondition (which principal classes may call), so both when-to-use and eligibility are covered.

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