List configured currencies with exchange rates to retrieve current currency data for accounting operations. Use filters and pagination to narrow results.
List configured currencies with exchange rates. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | ||
| take | No | ||
| order | No | GraphQL order clause | |
| where | No | GraphQL where filter |
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 behavioral burden. It explicitly states 'Read-only,' which is the key side-effect disclosure for a list tool. It does not mention pagination limits, filtering syntax, or authentication assumptions, but those are either present in the schema or implicit for a simple list operation.
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?
Only two short sentences, with the core behavior first and the safety qualifier second. Every word earns its place; there is no redundant or filler text.
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 low-complexity read-only list, the description names the return content (currencies and exchange rates) and the operation's safety. The schema covers the four optional parameters, so the definition is adequate for an agent to understand the tool's role and invoke it correctly.
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 description adds no parameter-level detail, but order and where already have descriptions in the schema as GraphQL clauses, and skip/take are standard pagination parameters with defaults and bounds. The missing parameter information in the description is therefore not a significant barrier to correct invocation.
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?
Description uses a specific verb ('List') and a precise resource ('configured currencies with exchange rates'), and the read-only clause clarifies the operation. This is distinct from sibling list tools that target other master-data resources such as m3_countries or m3_vat_classifications.
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 use when the agent needs to retrieve configured currencies with exchange rates, and the read-only label signals it is a safe retrieval rather than a mutation. It does not explicitly name alternatives or exclusion conditions, but no sibling tool appears to offer a currency-list alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.