Mercury Multiorg MCP

Overview Schema Source Related Servers Discussions Admin

list_statements

Read-onlyIdempotent

Retrieve monthly statement metadata for a Mercury checking or savings account, including statement IDs and periods, to locate documents before downloading PDFs.

Instructions

List one account's monthly statements (metadata only) in Mercury API desc order.

    Use this for statement ids and periods of a checking or savings
    account; use `list_treasury_statements` for treasury accounts, which
    this endpoint does not serve, and `get_statement_pdf` (when enabled)
    for the document itself. Credit accounts are documented as
    unsupported, though Mercury's changelog suggests credit statements may
    be served; if so, only the depository fields surface. Account number
    and EIN are masked to their last four; routing number, address,
    download URL, and the per-statement transaction list are not returned
    (`transactionCount` summarises the last). `start`/`end` may span at
    most 3 months (Mercury's rule) and must be real calendar dates with
    `end` not before `start`, all checked here before any request; Mercury
    treats a future `end` as today.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	Latest statement period start, YYYY-MM-DD.
`limit`	No	Maximum statements to return (Mercury API desc order).
`start`	No	Earliest statement period start, YYYY-MM-DD. With `end`, at most 3 months apart.
`entity`	Yes	Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default.
`account_id`	Yes	Checking or savings account id from `list_accounts`.

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 already declare read-only, idempotent, open-world, and non-destructive traits. The description adds substantial context beyond annotations: metadata-only responses, masking of account number/EIN to last four, excluded fields, transactionCount summarizing the transaction list, and specific date-bound validation rules. No contradiction with annotations.

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?

Front-loaded with the core purpose, then uses compact sentences to convey alternatives, exclusions, masking, and validation rules. No filler; every sentence earns its place by contributing to correct invocation.

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?

An output schema exists, so return fields need not be restated. The description covers all critical behavioral expectations, edge cases, exclusions, and validation rules an agent needs for correct invocation, making it complete for a tool of this complexity.

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 description coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining start/end constraints (at most 3 months apart, real calendar dates, end not before start, future end treated as today) and clarifying entity/account_id provenance from list_entities/list_accounts, raising it above baseline.

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, and scope: 'List one account's monthly statements (metadata only) in Mercury API desc order.' It explicitly names sibling tools it is not (list_treasury_statements, get_statement_pdf), making its purpose unambiguous and distinct from related endpoints.

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?

Provides explicit routing: use this for checking/savings statements, list_treasury_statements for treasury accounts, and get_statement_pdf for the document itself. It also covers the credit-account edge case, leaving no doubt about when this tool should be selected over alternatives.

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