Skip to main content
Glama

x420_currency_convert

Convert an amount between major fiat currencies using European Central Bank daily reference rates for the latest or a historical date.

Instructions

Currency converter (ECB rates): Converts an amount between ~30 major fiat currencies using European Central Bank daily reference rates (frankfurter.dev, free, no key), latest or for a past date. Source: ECB via api.frankfurter.dev. Reference rates, not a dealable quote. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: amount, from, to, rate, result, date, source - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"amount":"100","from":"USD","to":"EUR"}.

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>",
      "to": "<to>"
    },
    "name": "x420_currency_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesISO 4217 code, e.g. EUR
dateNoYYYY-MM-DD for a historical rate (default latest)
fromYesISO 4217 code, e.g. USD
amountNoamount to convert (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the material behaviors: the call costs $0.02 USDC settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY, real money moves, and each response returns the deliverable plus a signed receipt and settlement transaction. It also names the upstream source and its license-free, keyless nature. This is exactly the context annotations cannot convey.

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-loaded with the capability, then pricing, then return shape, then example — a sensible order for an agent scanning quickly. The multi-category legal disclaimer ("professional, legal, insurance, engineering, medical, financial or tax advice") is boilerplate that could be trimmed without losing agent-relevant meaning.

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 carries the return contract itself and does so — enumerating amount, from, to, rate, result, date, source plus receipt and settlement transaction. Combined with cost, auth source, upstream provider, and a worked example, an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the schema already documents all four parameters, setting the baseline at 3. The description adds value by giving a concrete example input that shows amount as a string alongside from/to, reinforcing the required/optional split. It doesn't clarify precision or rounding behavior for the conversion.

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?

The description opens with a specific verb and resource — "Converts an amount between ~30 major fiat currencies" — and names the exact data source (ECB daily reference rates via frankfurter.dev). It also bounds scope explicitly (fiat only, ~30 currencies), which separates it from the sibling unit and time-zone converters without naming them.

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

Usage Guidelines4/5

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

It states the two supported modes clearly (latest rate, or a historical rate via a date field) and warns that these are reference rates, not a dealable quote, which tells the agent when the output is inappropriate for trading decisions. It stops short of explicit when-not-to-use guidance or pointing at an alternative for spot/crypto quotes.

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