Skip to main content
Glama

SouthPow crypto & market data

buy_fx_huf

Paid. Forex rates from HUF to 29 other currencies, latest ECB reference fix. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/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_huf"
  }
}

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?

With no annotations, the description carries the full burden and does a solid job: it discloses the price ($0.01 USDC), accepted payment chains (Base or Solana), that failures are not charged, and the data provenance ('latest ECB reference fix'). It does not explain the payment handshake (how the USDC is actually charged, e.g., x402 flow) or rate freshness/latency, but the commercial behavior is unusually well disclosed.

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?

Front-loads the crucial fact ('Paid.') and packs price, rails, auth, refund policy, and source into a few short clauses with no filler. The telegraphic style and trailing bare URL are slightly terse but not wasteful.

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, zero-param tool with no output schema and no annotations, the description covers cost and provenance but never sketches the response (e.g., a map of 29 currency codes to rates) or how the micropayment is executed. Those gaps matter because an agent must decide whether the call is affordable and how to parse the result.

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 there is nothing for the description to disambiguate; baseline is 4. It correctly implies the fixed base currency is baked into the endpoint rather than configurable.

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 and resource: 'Forex rates from HUF to 29 other currencies' from the ECB reference fix. The explicit direction (HUF as base) is the key differentiator among the many sibling fx tools such as buy_fx_eur_huf and buy_fx_usd_huf, though those alternatives are never named.

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?

Prerequisites are covered well (paid, no account, no API key), which tells the agent it can call this without setup. But there is no explicit when-to-use vs. when-not guidance — e.g., that buy_fx_eur_huf or buy_fx_usd_huf should be preferred for inverse or USD-based quoting — so selection among the ~60 sibling fx tools is left 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.

Resources