Skip to main content
Glama

ledger_history

Read-onlyIdempotent

Read a scenario's public adoption history—current base, base chain, queued runner-ups, and append-only events—to audit what was adopted or reverted and when.

Instructions

Read the public lineage: current base, base chain (initial version plus every adoption and revert), queued runner-ups and the append-only public event list. Use it to audit what was adopted and when; use meta_metrics for aggregate rates. Read-only; private confirmation and final events are hidden. Returns {current, base_chain, runner_ups, events}.

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": {
      "config": "<config>"
    },
    "name": "ledger_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesPath of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / config / description
      Added value: +"Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path."
  2. First observedv0.1.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: the lineage is 'public', private confirmation and final events are deliberately hidden, and the event list is append-only — a data-visibility caveat an agent would otherwise miss. It does not discuss ordering or pagination of the event list.

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 sentences, front-loaded with the resource and its parts, then usage routing, then behavioral caveats, then return shape. The parentheticals ('initial version plus every adoption and revert') resolve ambiguity rather than add bulk, and nothing is redundant with the structured fields.

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?

With no output schema, the description usefully names the returned keys {current, base_chain, runner_ups, events}, and the single parameter is fully covered by the schema. Minor residual gaps remain around event ordering and what a 'queued runner-up' means, but nothing needed to invoke the tool correctly is missing.

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?

There is a single parameter, config, and schema description coverage is 100%, so the path semantics and the server's --config restriction are already documented in the schema. The description adds no meaning about this parameter, making the baseline 3 appropriate rather than a penalty.

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 ('Read') and a precisely scoped resource ('the public lineage'), then enumerates its components: current base, base chain with adoptions and reverts, queued runner-ups, and the append-only event list. An agent can distinguish this from siblings such as version_current or run_results 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 Guidelines4/5

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

Gives an explicit use case ('audit what was adopted and when') and names a concrete alternative with its own purpose ('use meta_metrics for aggregate rates'), which cleanly separates historical detail from aggregate statistics. It stops short of stating when this tool should NOT be used, so it falls just shy of full when/when-not coverage.

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