Skip to main content
Glama

textokit_fx_rates

FX rates: daily exchange rates for USD, EUR, ARS, BRL and 160 currencies. 0.001 USDC per call (x402, Base), first 10 calls/day per IP free; an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "textokit_fx_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency, ISO 4217 (default USD).USD
quotesNoComma-separated quote currencies, 1 to 20 ISO 4217 codes.EUR,GBP,BRL,ARS,MXN,JPY
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
  3. First observed

TDQS

A3.9/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 well: it discloses pricing model, rate limit (10 calls/day per IP), failure behavior (unpaid call returns x402 payment requirements), and warns about the payment signature ('never a private key'). It does not describe rate freshness/caching or the response shape, keeping it below 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?

Two dense sentences, front-loaded with purpose before commercial terms. Every clause (coverage, price, free tier, unpaid behavior, sample pointer) carries operational value; only the currency enumeration is slightly redundant with the schema defaults.

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 zero-required-parameter pricing/rates tool with no output schema and no annotations, the description covers the commercial and failure paths an agent needs to act correctly. It omits what the returned rates look like and whether any historical date can be requested, a modest gap.

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%, and the schema itself documents base, quotes, and the x402 payment payload in detail. The description adds no syntax or format detail beyond what the schema provides, so baseline 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?

Opens with a specific verb+resource: 'FX rates: daily exchange rates' with currency examples (USD, EUR, ARS, BRL) and coverage (160 currencies). This clearly separates it from crypto_prices and dolar_ar by domain. It does not explicitly name those siblings, so it stops short of a 5.

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 concrete usage context: free tier of 10 calls/day per IP, then paid at 0.001 USDC, and routes free exploration to textokit_sample. It states the condition under which an unpaid call is acceptable/expected but does not explicitly say when to prefer dolar_ar or crypto_prices over this tool.

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.