Skip to main content
Glama

X420 agent services

x420_currency_convert

Read-onlyIdempotent

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. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: amount, from, to, rate, result, date, source.

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 observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: it discloses that this hosted endpoint does not return data, only payment instructions (pay_to, network, price, x402 URL), the exact 402 retry sequence with PAYMENT-SIGNATURE, the $0.02 USDC cost on Base, and the JSON fields delivered after payment. It also correctly warns the rates are reference rates, not a dealable quote.

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

Conciseness3/5

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

Purpose and price are front-loaded and the payment flow is ordered logically, but the block runs long as a single paragraph mixing purpose, a broad legal disclaimer, pricing, transport mechanics and output shape. The 'Not professional, legal, insurance, engineering, medical, financial or tax advice' sentence is boilerplate that dilutes the operational content.

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?

Covers the essentials for a paid, non-obvious tool: what it validates, what it returns unpaid, how to pay, and what the paid deliverable contains — compensating for the absent output schema. It omits failure behavior, such as what happens with an unsupported currency code or an invalid date.

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 baseline is 3, but the description adds meaning the schema lacks: the currency universe is limited to ~30 major fiat currencies on ECB rates, and date means an ECB reference date rather than an arbitrary timestamp. It does not add format detail for amount beyond the schema's string type.

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?

States a specific verb and resource ('Converts an amount between ~30 major fiat currencies') plus the source of truth (ECB daily reference rates via frankfurter.dev) and the scope (latest or historical). This is clearly distinct from siblings like x420_units_convert or x420_time_zone-convert, so an agent can select it without opening the schema.

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?

Explains the conditions of use well: latest rate vs a past date via the date parameter, and the two routes to actually obtaining the deliverable (pay the x402 URL manually, or run the local x420-mcp server with your own wallet key). It does not state when NOT to use it (e.g. crypto pairs or non-ECB currencies), which keeps it short of a 5.

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