Mercury Multiorg MCP

Overview Schema Source Related Servers Discussions Admin

list_accounts

Read-onlyIdempotent

Lists a Mercury organization's accounts with available and current balances, providing masked account IDs needed for transactions, statements, and cards.

Instructions

List one organization's Mercury accounts with available and current balances.

    Use this for account ids (`list_transactions`, `list_statements`, and
    `list_cards` take them); use `list_credit_accounts` for credit accounts
    and `list_treasury` for treasury accounts. Every page of `GET /accounts`
    is walked. Account numbers are masked to their last four digits;
    routing numbers are not returned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entity`	Yes	Exact `entity` key from `list_entities`, not its `display_name`. Required; there is no default.

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

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description reveals important behavior: every page of GET /accounts is walked, account numbers are masked to the last four digits, and routing numbers are not returned. This gives the agent concrete expectations about data completeness and privacy handling.

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 compact and front-loaded with the core purpose, followed by directly useful usage guidance and behavioral caveats. Every sentence contributes information an agent needs to select and call the tool correctly.

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?

Given the output schema, annotations, and single well-documented parameter, the description fully covers the key context: what the tool returns, how to use it with downstream tools, which alternatives exist, and important masking/pagination behaviors.

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 coverage is 100%, and the parameter description already explains that `entity` must be the exact key from list_entities, not display_name, and that it is required. The tool description adds no further parameter detail, so the 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 opens with a specific verb and resource: 'List one organization's Mercury accounts with available and current balances.' It also distinguishes itself from list_credit_accounts and list_treasury, making its scope clear.

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 (to obtain account ids for list_transactions, list_statements, and list_cards) and names the alternatives for credit and treasury accounts, leaving no ambiguity about routing.

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