Skip to main content
Glama

Agent Exchange store

fx_history

$0.002 via x402: Daily ECB reference rate history for a pair over the last N business days (up to 365): {from, to, days, series:[{date, rate}]}. Pay 0.002 USDC through https://store.agentexchange.work/gw/fx/history?from=EUR&to=USD&days=30. Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
toYesto
daysNo1..365, default 30
fromYesfrom
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose the critical behavioral trait: this is a paid x402 tool costing 0.002 USDC, settled via Coinbase through the Agent Exchange gateway, with the request URL spelled out. It omits rate limits and how long a signed payment remains valid, keeping it from 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?

Three tight sentences with no filler; every clause carries information (price, purpose, output shape, payment endpoint). Front-loading the price ahead of the purpose is slightly odd, but the definition stays compact and readable.

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?

Even without an output schema, the description conveys the response shape ({from, to, days, series:[{date, rate}]}), the day bound, and the full payment flow, which an agent needs to call a metered endpoint correctly. Only edge behavior (payment expiry, error/pricing response semantics) is unstated.

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 coverage is 100%, so the schema already documents from, to, days, and x_payment, establishing a baseline of 3. The description reinforces invocation with a concrete example URL (from=EUR&to=USD&days=30) and the series:[{date, rate}] return shape, but adds little parameter meaning beyond the schema.

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?

States a specific resource and scope: daily ECB reference rate history for a currency pair over N business days (bounded at 365). The historical-series framing distinguishes it in spirit from fx_rates/fx_convert, but it never names those siblings, so an agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says when to pick fx_history over fx_rates or fx_convert, nor what the payment precondition implies for callers. The only guidance is the days cap of 365, which is a constraint rather than usage direction.

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