Skip to main content
Glama

Lilambd Data for Agents

fx-rates

What is this amount worth in another currency today, and how fast is each currency losing value?. Converts an amount between 30 currencies at the latest ECB reference rate (cross via EUR), adds USD/EUR equivalents and each issuer's headline CPI inflation (1y, 5y, purchasing power left). Computed by Lilambd from ECB and World Bank data. Routes: /answer (from*, to*, amount); /currencies (limit). Paid $0.05 USDC per call via x402 (_meta["x402/payment"]); set sample=true for a free 3-row preview.

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": {
      "route": "<route>"
    },
    "name": "fx-rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /answer, /currencies. Replace {placeholders} with a value, e.g. /search or /HND.
paramsNoQuery parameters, e.g. {"q":"tokyo","limit":"50"}
sampleNoFree preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavioral burden and does notable work: it discloses the $0.05 USDC per-call cost via x402 (_meta["x402/payment"]), the free 3-row sample escape hatch, the data provenance (ECB and World Bank), and the computation path (cross via EUR). It does not cover rate limits, error behavior, or staleness of the 'latest' rate, which keeps 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?

The definition is front-loaded and dense with useful facts; cost, free preview, and route signatures are all present without filler. The opening rhetorical question is a slightly wasteful flourish, and the middle sentences pack multiple facts per clause, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, multi-route tool with a nested params object and no output schema, the description should describe what comes back. It gestures at the payload (USD/EUR equivalents, CPI 1y/5y, purchasing power left) but never gives the actual response shape or field names, so an agent cannot predict the return structure. Payment, provenance, and routing are well covered; the return contract is the gap.

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, and the description earns an upgrade: it enumerates the route values and binds each to its query parameters (/answer needs from*, to*, amount; /currencies takes limit), which the schema's generic additionalProperties string map does not convey. It also explains sample=true as a max-3-row free preview beyond the schema's terse 'Free preview, max 3 rows'. Currency code formatting for from/to is still left implicit.

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?

The description gives a concrete verb and resource: converting an amount between 30 currencies at the ECB reference rate, with USD/EUR equivalents and CPI inflation layered on. It also names the exact routes (/answer, /currencies), so an agent knows what the tool does and which sub-operation to pick. It stops short of differentiating itself from look-alike siblings such as exchanges, budget-inflation, or local-markets.

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?

Guidance is implied through the route list and the free-preview tip: an agent can infer that sample=true is the way to test without paying and that /currencies lists supported codes. But there is no explicit 'use this when...' statement, no stated exclusions, and no comparison to related tools. The routing hints are useful yet fall short of true selection guidance.

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