CurrencyCore

Currency reference

list_currencies

Read-onlyIdempotent

Return the full ISO 4217 currency catalogue as an array of { code, numeric, name, symbol }. Use to resolve a currency name or symbol to its code, or to confirm a currency is supported before calling another tool, so a typo fails at selection rather than silently. Use list_countries for country codes. Non-ISO codes CNH, GGP, IMP, and JEP have an empty numeric. Returns the full list in one call and takes no parameters. Public tool: no sign-in and no API request billed.

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": "list_currencies"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond that: no sign-in required, no billed API request, the whole list returned in one call (no pagination), and the edge case that non-ISO codes CNH/GGP/IMP/JEP have an empty `numeric`. Missing only failure/error behavior, which keeps it short of a 5.

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?

Return shape is front-loaded, then usage, then the sibling redirect, then edge cases and access notes. Every sentence carries distinct information and none repeat the annotations or the empty schema.

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

Completeness5/5

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

With no output schema, the description supplies the return shape itself, plus the non-ISO `numeric` caveat and the no-billing/no-auth facts. Nothing an agent needs in order to call this correctly and interpret the result is absent.

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

Parameters4/5

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. The description confirms this explicitly ('takes no parameters') and instead spends its words on return-field semantics, which is the right allocation for a no-arg listing tool.

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

Purpose5/5

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

Names a specific verb (return) and resource (full ISO 4217 currency catalogue) and states the exact record shape `{ code, numeric, name, symbol }`. It also names the sibling it is not (`list_countries` for country codes), so an agent can distinguish it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives two concrete use cases (resolve a name/symbol to a code, pre-validate support before calling another tool) plus the rationale (fail at selection rather than silently). It explicitly redirects country-code lookups to `list_countries`, which is the closest risk of misfire.

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

All CurrencyCore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?