Retrieve retailer account details, including name, currency, time zone, and settings. Call first when you need the store’s currency or local time zone for accurate reporting.
Retailer account details: name, currency, time zone, settings. Call this first if you need the currency or local time zone.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only the minor insight that this is a cheap-looking first call and what fields come back; it says nothing about failure modes (e.g. no configured retailer) or freshness of the settings.
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 short sentences, front-loaded with the payload description and followed by the sequencing advice. Nothing is redundant with the schema or annotations.
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?
An output schema exists, so return values need no explanation, and the description still names the key fields for quick scanning. Only the missing edge-case behavior (what happens if no retailer is configured) keeps it from a 5.
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 is 4; there is nothing the description could clarify about arguments. The mention of currency/time zone correctly implies no filtering input is needed.
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+resource and enumerates the returned fields (name, currency, time zone, settings), which clearly distinguishes it from sibling list/get tools like api_get or list_outlets. Lacks an explicit statement of what a 'retailer' scopes (single account vs collection), so it stops short of a 5.
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?
'Call this first if you need the currency or local time zone' is an explicit when-to-use directive that tells the agent to bootstrap from this call rather than fetching it later. It gives no when-not guidance or named alternatives, which keeps it below a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.