Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Currency exchange rates, forex: currency converter and conversion

fx
Read-only

Foreign exchange rates from the European Central Bank for about 30 major currencies (USD, EUR, GBP, JPY, CHF, SEK, CAD, AUD, CNY, INR, BRL and more). Give a base currency, optionally the target currencies and an amount, and get the rates, the converted amounts and the date the rates apply to. Use for currency conversion, invoice and price calculations, and reporting in another currency. Example: from=USD. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>"
    },
    "name": "fx"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional comma-separated target currency codes, e.g. EUR,GBP; default is all available currencies
fromYesBase currency as a three-letter ISO 4217 code, e.g. USD (an HTTP call with no input at all answers for USD)
amountNoOptional amount of the base currency to convert (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description still adds genuinely new context: the ECB as data source, explicit per-call pricing ($0.002 via x402 USDC or card key, first 25 free, failed calls free), and that it computes only. That pricing detail matters given idempotentHint=false, since repeats cost money. It does not describe failure modes or rate-limit behavior, so it is not 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.

Conciseness4/5

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

Front-loads the data source and currency coverage, then the call shape, then use cases, then commercial terms, which is a sensible order. A few phrases are expendable, notably "and more" after the currency list and the somewhat chatty billing sentence, but nothing is genuinely misleading or padded at length.

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?

With no output schema, the description usefully states what comes back: rates, converted amounts, and the date the rates apply to. Combined with the source and cost disclosure, an agent has enough to call correctly. The remaining gap is sibling disambiguation rather than tool mechanics.

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?

Schema description coverage is 100%, with each of from, to and amount documented including the ISO 4217 format, comma-separated targets, and default of 1. The description restates the same shape (base currency, optional targets, optional amount) without adding syntax or constraint detail, so the baseline of 3 applies.

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: European Central Bank foreign exchange rates for ~30 named major currencies, plus rate lookup and amount conversion. An agent immediately knows what the tool returns. It stops short of 5 because it never differentiates itself from adjacent siblings such as fx_rates, fx_all, or fx_symbols, leaving overlap unaddressed.

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?

Offers concrete use cases (currency conversion, invoice and price calculations, reporting in another currency) and a minimal example (from=USD), which implies when to reach for it. It gives no when-not guidance and no routing to the sibling FX tools that appear alongside it, so an agent choosing among them is still guessing.

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.