Retrieve full details of a Mercury account using its account ID, returning balances, routing and account numbers, status, nickname, and type.
Retrieve details of a specific Mercury account by its account ID. Returns accountNumber, availableBalance, currentBalance, dashboardLink, legalBusinessName, name, nickname, routingNumber, status, and type.
| Name | Required | Description | Default |
|---|---|---|---|
| accountId | Yes | The Mercury account UUID. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It documents the return fields but says nothing about authentication, error behavior when the account ID is invalid, or whether field values may be null/optional.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two dense sentences, front-loaded with the action and followed by the return payload, with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read tool with no output schema, the description supplies the full field list, which is genuinely useful. Minor gaps remain around error/auth behavior, but the operational core is complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description only repeats that the ID identifies the account and adds no format or constraint detail beyond the schema's 'Mercury account UUID'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Retrieve) and resource (Mercury account) scoped by account ID, and it enumerates the returned fields, making it clearly distinguishable from siblings like get_accounts or get_account_statements.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage via 'by its account ID' and by contrasting with the list-oriented sibling get_accounts, but it never states when to use this tool versus alternatives or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.