List all supported currencies. Returns every supported ISO 4217 currency code with its full English name. Returns: Map of currency code to currency name..
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the return value is a map of currency code to name, providing useful context beyond annotations. No contradictions.
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?
The description is brief and front-loaded with the main verb. However, the second and third sentences are somewhat redundant (both mention code and name), and there is a minor typo with double period.
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?
No output schema exists, so the description carries the burden of explaining return values. It states the map structure and content, and for a zero-parameter read-only tool this is sufficient.
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 has zero parameters, so the baseline is 4. The description accurately describes the fixed output without needing parameter clarification.
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?
The description clearly states the tool lists all supported currencies, providing ISO 4217 codes and English names. This distinct purpose is obvious against sibling tools that focus on rates.
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 states what the tool does but offers no explicit comparison to get_historical_rates or get_latest_rates. Usage context is implied by the tool name and sibling set, but no when-to-use vs alternatives guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinctly different purpose: listing available currencies, fetching historical rates, and fetching latest rates. No overlap or ambiguity exists between them.
All tools follow the consistent verb_noun pattern 'get_' + resource (currencies, historical_rates, latest_rates). This makes the API predictable and easy to navigate.
With only 3 tools, the server is tightly scoped to its purpose of providing ECB reference rates. Each tool is essential and contributes to a well-rounded API without unnecessary bloat.
The server fully covers the domain of ECB reference rates: you can list supported currencies, retrieve latest rates, and retrieve historical rates. No obvious gaps exist for the stated purpose.