Skip to main content
Glama

ECB Euro FX Reference Rates Payment Quote

ecb_fx_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/fx/ecb (base $0.005; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET with no parameters (all published rates), or ?symbols=USD,GBP. ECB euro reference rates per 1 EUR with the fix date; optional symbols=USD,GBP. Not affiliated with the ECB. Information only, not for transaction pricing. Bad input or source down: not charged. USDC on Base. Source: European Central Bank (ECB), euro foreign exchange reference rates. This information can be obtained at no cost directly from the ECB website, ecb.europa.eu: https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (native USDC), a request is settled only when it succeeds (HTTP status belo

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds substantial non-obvious behavior: the $0.005 base price, that the tool never executes the check or pays, and chain-specific charging rules (Base errors uncharged, Solana/XRP failed requests may still be charged, Polygon settles only on success). This is exactly the billing risk context an agent needs before invoking a paid route, though the text is truncated mid-sentence and repeats 'USDC on Base' twice, leaving the Polygon clause incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a run-on that mixes payment mechanics, data provenance, legal disclaimers, and per-chain settlement rules without ordering or separation, and it terminates abruptly ('HTTP status belo'). Redundant material — repeated 'USDC on Base', the full ECB URL plus a second attribution sentence — crowds out the front-loaded purpose.

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 payment-gated quote tool with no output schema, the description covers cost, charging behavior, and data source well. It does not describe the shape of the returned payment terms (what fields, currency, expiry), and the truncation means at least one settlement rule is cut off, so an agent still lacks a complete picture of the response and the Polygon path.

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?

The input schema is an empty object, so the baseline is 4. The description nonetheless documents the real query interface the agent must use downstream ('?symbols=USD,GBP', or no parameters for all published rates), which is meaningful semantic information the schema cannot express. The mild downside is that this creates an apparent mismatch with the zero-parameter MCP schema, which is not reconciled.

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 opening clause states a specific verb and resource: 'Returns the payment terms for https://horizonpulse.dev/api/fx/ecb'. Combined with the name and the sibling *_quote family, an agent can identify this as the ECB FX data quote endpoint. The clarity is undercut by the description drifting into describing the underlying rates and source attribution rather than the tool's own function, but the core purpose is recoverable.

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?

It gives procedural usage of the paid endpoint ('Pay the 402 over HTTP with x402 v2: GET with no parameters ... or ?symbols=USD,GBP') and caveats ('Information only, not for transaction pricing', 'Not affiliated with the ECB'). What it never states is when an agent should pick this tool over the many sibling *_quote tools, or that a quote must precede payment; usage is implied rather than contrasted.

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.