Skip to main content
Glama

Currency Conversion Payment Quote

fx_convert_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/fx/convert (base $0.002; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?from=USD&to=JPY&amount=100 (EUR or one of 29 ECB currencies). Currency conversion: convert an amount between EUR and 29 currencies, or between two of them, at the latest ECB euro reference rates, with the rate date and the rates used. Converted amounts and cross rates are calculated by Horizon Pulse, not published by the ECB. Not affiliated with the ECB. Information only, not for transaction pricing. Bad input or source down: not charged. USDC on Base. Free at ecb.europa.eu.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already cover read-only, idempotent, non-destructive, and closed-world traits, and the description adds real value beyond them: exact pricing, USDC-on-Base-only settlement, the x402 v2 payment protocol, and a billing policy for failures ('Bad input or source down: not charged'). It also discloses data provenance (ECB reference rates, cross rates computed by Horizon Pulse, not ECB-published). The main remaining gap is that it never says what form the returned terms take.

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

Conciseness3/5

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

The purpose and price are front-loaded, which is good, but the text is a long run-on that repeats itself: 'USDC on Base' appears twice, and the 'EUR or one of 29 ECB currencies' scope is stated more than once. Disclaimers ('Not affiliated with the ECB', 'Information only, not for transaction pricing') are useful but padding the middle of the description rather than being grouped at the end.

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-parameter, read-only quote tool with annotations and no output schema, the description covers pricing, currency scope, data source, payment mechanics, and failure billing, which is most of what an agent needs to decide and act. The missing piece is any indication of the fields the returned payment terms contain.

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 tool takes zero parameters, so the baseline is 4. The description uses the space to document the query convention of the quoted endpoint (from/to/amount, e.g. GET ?from=USD&to=JPY&amount=100), which is contextual help even though it is not a parameter of this tool.

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 states a specific verb and resource: it 'Returns the payment terms' for the fx/convert endpoint, with the price ($0.002) and settlement asset (USDC on Base). It also describes the underlying conversion capability (EUR to 29 ECB currencies at ECB reference rates), but blends the quote-tool purpose with the API it describes, so an agent must disentangle which part is this tool versus the HTTP call it quotes.

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 clearly states what the tool does NOT do ('never runs the check or pays') and gives the follow-up action (pay the 402 over HTTP with x402 v2), which implicitly tells an agent to call this first when payment terms are needed. However there is no explicit when-to-use comparison against the sibling ecb_fx_quote beyond the closing 'Free at ecb.europa.eu', leaving the alternative-route decision to inference.

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.