Mercury Multiorg MCP

Overview Schema Source Related Servers Discussions Admin

list_treasury_transactions

Read-onlyIdempotent

Retrieve a treasury account's ledger transactions, newest first, with optional date-range filtering and exact truncation for pagination.

Instructions

List one treasury account's ledger transactions in Mercury API desc order, optionally within a day range.

    The API has no date filters for this endpoint and documents no sort
    key, so with `start` or `end` the whole ledger is walked (up to 200
    pages of 1000), filtered on `canonicalDay` here, and sorted newest
    first before `limit` applies; `truncated` is then exact. Without a
    window the Mercury API `desc` order is returned as is. Use this for
    one treasury account's ledger; use `list_transactions` for the
    organization's bank-account transactions.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	Latest canonicalDay, YYYY-MM-DD (inclusive).
`limit`	No	Maximum transactions to return (windowed: newest first; else Mercury API desc order).
`start`	No	Earliest canonicalDay, YYYY-MM-DD (inclusive).
`entity`	Yes	Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default.
`treasury_id`	Yes	Treasury account id from `list_treasury`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.6Sep 15, 2026

changedInput schema / properties / entity / description

Previous value: -"Entity key from `list_entities`. Required; there is no default."New value: +"Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default."

First observedv0.1.4Sep 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare readOnlyHint and idempotentHint, but the description adds significant behavioral detail: the API lacks date filters, so with start/end it walks up to 200 pages of 1000, filters on canonicalDay, sorts newest-first, and makes 'truncated' exact. Without a window, it returns the API's desc order as-is. This goes well beyond the annotations and discloses edge cases and pagination behavior.

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?

The description is front-loaded with the core purpose, then uses a second paragraph for the important behavioral caveats. Every sentence contributes to correct usage—no fluff. The structure separates the simple case from the windowed case clearly, and the sibling reference is placed at the end for context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters and 2 required, the description covers the unusual API limitations, the pagination strategy, sorting, and the truncation semantics. An output schema exists, so return format is covered. The tool's read-only and idempotent nature is already in annotations. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds context for 'start' and 'end' by explaining how they trigger a full ledger walk and the resulting sort and limit behavior. It also clarifies that 'entity' must be the exact key from list_entities. This adds value beyond the schema's own descriptions, justifying a 4.

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?

The description opens with a specific verb-resource pair: 'List one treasury account's ledger transactions'. It also explicitly contrasts with sibling 'list_transactions' for bank-account transactions, making the tool's scope unambiguous. The distinction is clear without needing to inspect 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?

It explicitly states when to use this tool ('Use this for one treasury account's ledger') and when to use an alternative ('use list_transactions for the organization's bank-account transactions'). It also explains the behavior when date filters are provided versus not, which guides correct invocation.

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