Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_huf

Paid. EUR/HUF exchange rate and inverse, latest ECB reference fix. $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/eur-huf.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 a solid job: it discloses that the call is paid, the exact price ($0.002 USDC), accepted chains (Base or Solana), that no auth is needed, and that failed calls are not charged. It stops short of describing caching/staleness of the ECB fix or what a payment failure looks like, which keeps it off 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.

Conciseness5/5

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

Telegraphic but disciplined: what it returns, the source, the price, how to pay, auth requirements, failure billing, and the endpoint, all in a few fragments with no filler. Front-loaded with the substantive content.

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, output-schema-less quote endpoint in a paid x402-style marketplace, this covers what an agent needs: what it returns, freshness source (ECB reference fix), cost, payment rail, and billing behavior on failure. The main omission is any statement of update cadence for the reference fix.

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 correctly adds nothing parameter-wise and instead spends its words on cost and source. Nothing suggests ambiguity in how to invoke it.

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 verb+resource ('EUR/HUF exchange rate and inverse') plus the data source ('latest ECB reference fix'), which is enough to distinguish it from the many buy_fx_* siblings, especially since the pair is named in the tool itself. It does not, however, explicitly contrast with adjacent pairs like buy_fx_eur, buy_fx_huf, or buy_fx_usd_huf, leaving the routing to inference from naming.

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?

Payment cost, accepted chains, and the no-account/no-API-key prerequisite are all spelled out, which is real usage context. But there is no explicit when-to-use guidance relative to the pair siblings (e.g. use this vs. build the cross-rate from buy_fx_eur and buy_fx_huf), so the selection logic is only implied by the pair name.

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