forex_currencies
Fetch the full list of currencies from Open Exchange Rates with your API key.
Instructions
List all currencies from Open Exchange Rates.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No |
Fetch the full list of currencies from Open Exchange Rates with your API key.
List all currencies from Open Exchange Rates.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description lacks behavioral details such as whether an API key is required, rate limits, or data freshness. Minimal disclosure beyond the basic purpose.
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?
Single sentence with no wasted words, but too brief for the context of many sibling tools and lack of output schema. Could be more informative while staying concise.
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?
The description does not explain the output format (e.g., list of currency codes or names). With no output schema, this information is missing. Overall incomplete for a tool with only a description.
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 schema has one parameter (api_key) with 0% description coverage, and the description does not mention it or add any meaning beyond the schema. Fails to compensate.
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 action (list) and the resource (all currencies) from a specific source (Open Exchange Rates). It distinguishes itself from sibling tools like forex_convert and forex_historical.
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?
No guidance on when to use this tool versus alternatives. With many sibling forex tools, explicit direction would be beneficial.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server