Skip to main content
Glama

fx

Convert between 30+ fiat currencies at the official ECB reference rate and retrieve optional historical rate dates for 0.001 USDC per successful Base call.

Instructions

Currency conversion at the official European Central Bank reference rate (via Frankfurter), with rate date. 30+ fiat currencies. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
toYesto
dateNooptional YYYY-MM-DD historical rate
fromYesfrom
amountNoamount

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/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 real work: it discloses the rate source, the cost (0.001 USDC on Base per successful call, x402), and the failure mode ('without a payment key this tool returns the 402 challenge'). Undisclosed: rounding, response shape, and the default when amount is omitted.

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?

Three short sentences, front-loaded with what the tool is, then scope, then cost and the auth failure condition. No filler and no repetition of the schema.

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 four-parameter read tool this covers source, universe, price, and payment gating, which is what an agent needs to decide and call. The one real gap is that nothing says whether amount is optional-with-default or how the result is rounded.

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%, but the schema's own descriptions are placeholders ('from', 'to', 'amount'), so the field-level documentation is thin. The description adds the meaningful constraint that values are among '30+ fiat currencies' and hints that a rate date is returned, but says nothing about amount defaulting or accepted formats.

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?

Names a specific verb and resource ('currency conversion'), pins the data source ('official European Central Bank reference rate via Frankfurter'), and bounds the currency universe ('30+ fiat currencies'). It stops short of differentiating itself from the sibling fx_history, so an agent must infer that one is a spot conversion and the other a time series.

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 only implied: the tool obviously applies when converting an amount between two currencies, and the payment note signals a precondition. There is no explicit when-to-use or when-not-to-use guidance, and no routing to fx_history for multi-date or historical lookups.

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