Retrieve Mercury organization details, including EIN, legal business name, DBAs, organization kind, and UUID for account setup or verification.
Retrieve information about the Mercury organization. Returns EIN, legal business name, list of DBAs (Doing Business As names with default flag), organization kind (personal/business), and organization UUID.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. "Retrieve" implies a safe read, and the list of returned fields adds real transparency about the response shape, but nothing is said about permissions, error behavior, or whether the org is inferred from the current credential.
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?
Front-loaded with the purpose, then a compact enumeration of return fields in a single sentence. No wasted words; the field list is dense but useful rather than 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?
With no output schema and no annotations, the description substitutes by enumerating the returned fields (EIN, DBA default flag, organization kind, UUID), which is exactly what an agent needs. It stops short of describing auth or default-org resolution, a minor gap.
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?
The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no inputs are needed, though it does not explicitly state that the organization is selected from the current session/credential.
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 (the Mercury organization) and enumerates the exact fields returned (EIN, legal name, DBAs, kind, UUID). No sibling tool covers organization data, so it is unambiguous among the listed get_* tools.
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?
Usage is implied by the description for a zero-parameter lookup, but there is no explicit statement of when to call this versus the sibling get_account/get_recipient tools or of any prerequisite (e.g., authentication or an org context). Adequate but with clear gaps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.