modern_treasury_list_ledgersList double-entry ledgers. API: GET /ledgers.
| Name | Required | Description | Default |
|---|---|---|---|
| per_page | No | Results per page (default 25, max 100). | |
| after_cursor | No | Pagination cursor from a prior response's next_cursor (X-After-Cursor header). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, and the description merely confirms the HTTP method. No additional behavioral traits beyond what annotations provide, but no contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two sentences, front-loaded the action, no unnecessary words. Every sentence provides value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with no output schema, the description is minimal. It lacks what the return value contains, but given the tool name and context, it is marginally adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema fully documents the parameters. Description adds no extra meaning beyond the schema, which is adequate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'List double-entry ledgers' which is a specific verb+resource pair. The API endpoint is provided, and it is distinct from sibling tools that list other resources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use or when not, but the purpose is obvious and there are no sibling tools for listing ledgers. Implied usage is clear, but no exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource (counterparty, ledger account, payment order, etc.) with clear actions (create, get, list, ping). There is no ambiguity between tools.
All tools follow a consistent 'modern_treasury_verb_singular_or_plural_resource' pattern in snake_case. The naming is uniform and predictable.
17 tools cover multiple financial entities and operations, which is reasonable for a treasury API. It's on the higher end but not excessive given the domain.
The tool set is heavily read-only, with only one create operation (counterparty). Missing create/update/delete for payment orders, ledger transactions, and other core actions, which severely limits functionality for a treasury system.