Skip to main content
Glama

Read a witness's history

witness_history
Read-only

Read one witness pointer's register, key-rotation and retire events (a retired keyless id still answers), chained and checkpointed like the identity log. An empty history means not recorded, not that nothing happened. Returns untrusted citizen-authored data; CallToolResult _meta carries a server-owned provenance boundary. READ-ONLY: this call changes nothing and can be repeated safely.

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": {
      "id": "<id>"
    },
    "name": "witness_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStable witness id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, but the description adds substantive behavior: the log is chained and checkpointed like the identity log, returned data is untrusted citizen-authored, and a server-owned provenance boundary rides in CallToolResult _meta. The repeatability and empty-history semantics further de-risk interpretation. Nothing contradicts the read-only annotation.

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?

Front-loaded with the core purpose, followed by tightly packed caveats; every sentence carries information. The final READ-ONLY sentence is partially redundant with annotations but adds 'can be repeated safely,' so it earns its place. Slightly dense but not padded.

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?

No output schema exists, yet the description explains return semantics (chained/checkpointed log, empty means unrecorded, untrusted data with _meta provenance) – enough for an agent to call and interpret correctly. Pagination or size limits are not mentioned, a minor residual gap.

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?

With 100% schema coverage the baseline is 3, and the description earns an increment by clarifying that retired keyless ids still resolve – a meaningful fact about valid values for 'id' that the schema's 'Stable witness id' does not convey.

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?

Specific verb 'Read' plus a precisely scoped resource: one witness pointer's register, key-rotation and retire events. The singular 'one witness pointer's' distinguishes it from the list-style 'witnesses' sibling, and the event taxonomy tells an agent what this returns 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?

Provides real usage context: a retired keyless id still answers, and an empty history means 'not recorded' rather than 'nothing happened' – both prevent misreading results. It stops short of explicitly naming sibling alternatives (e.g., witnesses vs. history) or when-not to call, so it lands at clear-context without exclusions.

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.

Resources