Skip to main content
Glama

An agent's latest statement

agent_statement
Read-onlyIdempotent

The latest 3-hour statement for one ranked agent: payments out split into spend, routing hops and payments whose receipt is not read yet; what left its control; income; open flags; the hash of the previous statement; and a Merkle proof against the window's Ed25519-signed root. Use this when you need the 3-hour statement with its Merkle proof; for the quick pre-payment view use pay_check, which includes it. A client that checks the statement itself: refuse if stale, if chain_ok is false, or if flags is not empty; then call find_agent and refuse if open_incidents is above zero. A statement covers a closed 3-hour window and publishes a few hours after it closes, so it cannot show the last few hours.

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": "agent_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAgent token id, slug or bound wallet (required; agent is accepted as the same field)
agentNoSame as id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / agent
      Added value: +{
      +  "description": "Same as id",
      +  "type": "string"
      +}
    • changedInput schema / properties / id / description
      Previous value: -"Agent token id, slug or bound wallet"New value: +"Agent token id, slug or bound wallet (required; agent is accepted as the same field)"
    • removedInput schema / required
      Removed value: -[
      -  "id"
      -]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: the statement covers a closed 3-hour window, publishes a few hours after it closes, therefore cannot show the last few hours, plus the staleness/chain_ok/flags checks a caller must perform. It stops short of describing the response shape or error behavior in detail.

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 resource and contents, then usage and caveats in descending importance, with no filler sentences. The dense semicolon list and the phrase 'use pay_check, which includes it' are slightly compressed, but every clause carries information an agent needs.

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 must convey what comes back, and it does so by enumerating the statement's components, plus window timing and verification steps. Remaining gaps are minor: exact field naming of the returned structure and failure modes are left implicit.

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?

Parameter count is 2 with 100% schema description coverage, including the documented id/agent alias, so the schema carries the semantics. The description adds nothing about the identifier itself; baseline 3 is appropriate.

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+resource: the latest 3-hour statement for one ranked agent, then enumerates what it contains (payments out split into spend/hops/unread receipts, out-of-control payments, income, flags, prior-statement hash, Merkle proof against the window's Ed25519-signed root). It explicitly distinguishes itself from pay_check, the quick pre-payment view, so an agent can choose 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 Guidelines5/5

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

Gives explicit when-to-use (need the statement with its Merkle proof) and names the alternative (pay_check) with the condition that selects it. It goes further and prescribes the client verification sequence: refuse if stale, chain_ok false, or flags non-empty, then call find_agent and refuse if open_incidents is above zero.

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.