Mercury Multiorg MCP

Overview Schema Source Related Servers Discussions Admin

list_treasury_statements

Read-onlyIdempotent

Fetch metadata for a treasury account's statements and tax documents (1099 and similar), filtered by document type. Find records without downloading files.

Instructions

List one treasury account's statements and tax documents (metadata only).

    Use this for treasury statement and tax-form (1099 and similar)
    metadata; use `list_statements` for checking and savings statements
    and `list_tax_docs` for recipients' W-9 forms. `document_type` is not
    validated here: a value outside Mercury's list is rejected by Mercury.
    Every page is walked. The API exposes these documents only through a
    presigned `downloadUrl`, which is not returned or fetched.
    `get_statement_pdf` (when enabled) may accept a treasury statement id
    (same id type as depository statements), but the docs do not promise
    it.

Input Schema

TableJSON Schema

Name	Required	Description
`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`.
`document_type`	No	Filter by document type. Omit for all.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.6Sep 15, 2026

changedInput schema / properties / document_type / description

Previous value: -"Filter by document type: MonthlyStatement, TradeConfirmation, 1099, 1099R, 1042S, 5498, 5498ESA, 1099Q, FMV, SDIRA. Omit for all."New value: +"Filter by document type. Omit for all."

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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavior beyond annotations: pagination is walked automatically, documents are only exposed via presigned downloadUrl (not returned/fetched), and the note about `get_statement_pdf` possibly accepting treasury ids. This is useful context not encoded in annotations.

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?

The description is well-structured and front-loaded with the primary purpose in the first line, then efficiently branches into usage distinctions and behavioral notes. It is slightly verbose (the `get_statement_pdf` aside is arguably tangential) but each sentence earns its place by conveying distinct, non-redundant information.

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?

Given the tool's moderate complexity (3 parameters, output schema exists, annotations cover safety), the description is nearly complete. It covers usage distinctions, pagination behavior, document_type validation, and the downloadUrl limitation. The only minor gap is that it does not describe the exact return structure, but the presence of an output schema offloads that responsibility. Overall, it gives an agent enough to call it correctly.

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% for all three parameters, so the schema already documents `entity`, `treasury_id`, and `document_type` with origins and constraints. The description adds minimal extra parameter semantics—it restates the treasury_id origin and document_type validation, but those are already in the schema. With full schema coverage, a baseline of 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?

The description states a specific verb and resource ('List one treasury account's statements and tax documents') and explicitly differentiates from sibling tools by naming `list_statements` and `list_tax_docs` with their distinct scopes. This gives an agent a clear, unambiguous purpose.

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?

The description provides explicit when-to-use guidance by contrasting with alternatives: 'Use this for treasury statement and tax-form metadata; use `list_statements` for checking and savings statements and `list_tax_docs` for W-9 forms.' It also clarifies a key behavior (`document_type` not validated locally) and page walking, so an agent knows exactly when to invoke this tool.

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