Skip to main content
Glama

apex-dev

Fx convert

fx_convert
Read-onlyIdempotent

Official ECB foreign exchange currency converter across 30+ major fiat currencies (USD, EUR, GBP, JPY, CHF, CAD, AUD, CNY, INR, BRL, etc.). Not financial advice. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional target 3-letter currency code or comma-separated list (e.g. USD or USD,GBP,JPY).
fromYes3-letter source currency code (e.g. EUR, USD).
amountNoOptional amount to convert (default 1).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds context those don't cover: the ECB data source, a fixed $0.001 per-call price, accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step payment handshake. The 'not financial advice' disclaimer is also relevant behavioral framing for a rates 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?

Three sentences, front-loaded with the capability and then the payment mechanics; nothing is padding. It is dense — the payment rail enumeration (Arc, Base, Solana, X1) could be trimmed — but every sentence carries operational value.

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?

No output schema exists, yet the description never says what a conversion returns (rates, converted amounts, multi-currency list behavior). Against that, the payment flow, pricing, and data provenance are all covered, so it is nearly complete for a simple read-only converter.

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%, so all four parameters (from, to, amount, payment) are already documented, which sets the baseline at 3. The description only marginally adds meaning — chiefly that `payment` must be obtained via a prior unpaid call — while `from`, `to`, and `amount` semantics are entirely carried by the schema.

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 — convert foreign exchange across 30+ major fiat currencies — and names the rate source (official ECB). It even enumerates representative currencies, so an agent can immediately tell this apart from siblings like whois_lookup or x402_price_comps.

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?

Gives an explicit, non-obvious call sequence: call once without `payment` to get terms, then again with `payment` to complete the paid conversion. What's missing is any when-not guidance or comparison to alternative tools, so it stops short of a full 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