Skip to main content
Glama

BRAINIAC Exchange Rates

List supported currencies

fx_currencies_list

Retrieve the list of supported currencies from the Frankfurter API. All currencies are ISO 4217 codes. Price $0.01 USDC. POST /api/v1/fx/currencies/list. Unpaid calls return 402 and do not run.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real value: cost ($0.01 USDC), the payment gate, and the exact failure mode ('Unpaid calls return 402 and do not run') — an agent knows it will not get data without paying. It does not state that the operation is read-only and side-effect free, and the 'POST' verb on a pure read is left unexplained, which is a notable omission for an unannotated tool.

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

Conciseness4/5

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

Five short sentences, front-loaded with purpose and format, followed by cost, endpoint, and failure behavior. Each sentence carries information; the raw endpoint path is the least useful line for an invoking agent but is harmless and aids debugging.

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 zero-param listing tool with no output schema and no annotations, the description covers purpose, data format, price, and failure behavior — enough to call it correctly. The residual gap is the exact response shape (flat array of code strings vs. objects), which is only hinted at by the ISO 4217 note.

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?

Zero parameters, so the baseline is 4. The note that results are ISO 4217 codes adds meaning about what the caller will receive, even though there are no inputs to disambiguate.

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?

States a specific verb and resource ('Retrieve the list of supported currencies from the Frankfurter API') and pins the content format ('All currencies are ISO 4217 codes'). The resource is inherently distinct from the fx_rates_* siblings, but the description never names or contrasts them, so it stops just 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?

Usage is implied rather than stated: an agent can infer this is the discovery call for valid currency codes before invoking fx_rates_convert or fx_rates_latest, but the description never says so. No exclusions, prerequisites, or when-not-to-use guidance are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources