Mercury Multiorg MCP

by dkaleganov

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_credit_accounts

Read-onlyIdempotent

Retrieve an organization's credit accounts with available and current balances by providing its exact entity key.

Instructions

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

    Use this for credit accounts only; use `list_accounts` for checking and
    savings accounts and `list_cards` for the cards themselves. Unpaginated
    `GET /credit` returns every credit account.

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

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the unpaginated nature of the endpoint ('Unpaginated GET /credit returns every credit account'), which is valuable behavioral context beyond the 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?

The description is compact and front-loaded: it states the purpose first, then provides usage guidance in a single follow-up sentence. No filler or redundant information.

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 tool's simplicity (one required parameter), the presence of an output schema, and annotations covering safety, the description is fully sufficient. The unpaginated note removes any ambiguity about return volume, and the sibling differentiation covers selection.

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?

The schema description covers 100% of the single parameter (entity) with detailed instructions about using the exact key from list_entities and noting it is required with no default. The tool description adds no further parameter semantics, so the baseline 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 (List), a specific resource (credit accounts), and the key data (available and current balances). It also explicitly distinguishes itself from sibling tools list_accounts and list_cards, making the purpose unambiguous.

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 when-to-use guidance: 'Use this for credit accounts only' and names the alternatives for other account types. It also clarifies the unpaginated behavior, giving the agent a complete decision framework.

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