Skip to main content
Glama

Get ledger

get_ledger
Read-onlyIdempotent

The append-only developmental ledger: every growth, pruning, and evaluation event with reasons (NG3 — returned verbatim).

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. The most ledger events to return. Default 100.
agent_idYesThe developmental agent's id, from create_agent.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"The developmental agent's id, from create_agent."
    • addedInput schema / properties / limit / description
      Added value: +"Optional. The most ledger events to return. Default 100."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely useful behavioral facts — the ledger is append-only (immutable history) and events are returned verbatim (no summarization or rewriting) — but says nothing about volume, pagination beyond the limit param, or ordering.

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?

A single front-loaded sentence with no filler; the content enumeration comes before the parenthetical. The 'NG3' token is internal jargon that costs a little clarity without earning its place.

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?

For a simple two-parameter read-only tool with an output schema and complete annotation coverage, the description supplies what the structured fields cannot: the meaning of the ledger and the verbatim, append-only nature of its entries. Ordering and pagination semantics are the only notable omissions.

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?

Schema description coverage is 100%: both agent_id (with its create_agent provenance) and limit (default 100) are documented in the schema. The description adds no further meaning about these parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (the append-only developmental ledger) and enumerates its contents: growth, pruning, and evaluation events with reasons. That is far more informative than the title 'Get ledger' alone, though the retrieval verb itself is only implied by the tool name and no sibling is named for contrast.

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

Usage Guidelines2/5

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

There is no explicit statement of when to call this versus alternatives such as describe_agent, export_state, or compute_efficiency_report. The agent must infer from the resource content that this is the raw audit-trail read, with no stated exclusions or prerequisites.

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.