Skip to main content
Glama

exchangerate_codes

Read-onlyIdempotent

Lists all supported currency codes and their names using an ExchangeRate-API key, so you can validate or map currencies in automation workflows.

Instructions

List all supported currency codes and their names. Requires an API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exchangerate_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoExchangeRate-API key (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.9
  2. Removed
  3. Addedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the authentication requirement, which is useful behavioral context. It does not describe rate limits, response format, or pagination, so it provides only moderate additional value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with no wasted language. The primary purpose is front-loaded, and the API key requirement follows efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with complete schema coverage and no output schema, the description states what is returned and notes the authentication requirement. It is nearly complete, though it could mention whether the result is a full list or paginated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter, api_key, and schema description coverage is 100%, so the schema already documents its purpose. The description repeats that an API key is required but adds no syntax or format details beyond the schema. Baseline 3 is appropriate when the schema carries the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb and resource: it lists supported currency codes and their names. This distinguishes it from sibling tools that fetch latest rates, convert currencies, or retrieve historical rates. It does not explicitly name those siblings, so it falls 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.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool should be used when you need the list of supported currency codes, but it does not state when to prefer it over alternatives such as exchangerate_latest or frankfurter_currencies. There are no explicit exclusions or usage conditions beyond the API key requirement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools