Skip to main content
Glama

ledger_report

Reports local executor usage and outcomes—tool calls, tokens, read/returned characters, model speed, quote-check failures, job outcomes/verdicts—so you can decide what to delegate and to which model.

Instructions

What the local executor did and what it saved: calls and executor tokens per tool, the characters it read against the characters returned to you (with a token estimate), and per model the speed, the share of quotes that failed the check, the outcome of delegated jobs and your verdicts. Use it to decide what is worth delegating, and to which model.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ledger_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it names the dimensions reported, including derived metrics (token estimate, share of failed quote checks, verdicts) that an agent could not guess. It never states the default lookback window or that the tool is a non-mutating read, so a few behavioral facts remain unstated.

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?

Two sentences, front-loaded with a plain summary ("What the local executor did and what it saved") before the detail list, and the second sentence is a pure call-to-action. The first sentence is a long colon-list that is dense but each item is load-bearing, not filler.

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?

An output schema exists, so return values need no prose treatment, and with one optional parameter this is a simple read-shaped report. The description covers enough for correct invocation except for the scope of the time window, which is the one omission that could cause a wrong call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is a `days` lookback with a default of 30, yet the description never mentions a time window at all — no default, no units, no maximum. The one thing the schema leaves unexplained is precisely what the prose omits, so the gap is not compensated for.

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?

The description enumerates the specific content of the report — per-tool calls, executor tokens, characters read vs. returned, per-model speed, quote-check failure rate, job outcomes and verdicts — so an agent knows exactly what resource this surfaces. It stops short of a crisp verb-first statement and never names the sibling tools it differs from (e.g., job_status or executor_status), so differentiation is inferential rather than explicit.

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?

"Use it to decide what is worth delegating, and to which model" gives a concrete decision context that rules out treating this as a job-monitoring tool. It offers no exclusions and no named alternative for single-job inspection, so the agent must infer that job_status handles one job while this handles aggregate history.

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