Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_huf

Paid. USD/HUF exchange rate and inverse, 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/usd-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_usd_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 itself discloses the important operational behavior: a $0.01 USDC charge, Base or Solana payment, no account or API key, and no charge for failed calls. It also identifies the source and endpoint, but omits payment-flow details, response structure, timestamp semantics, and any rate limits.

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?

The compact description front-loads its paid nature, then efficiently covers data content, cost, payment networks, access requirements, failure billing, and endpoint. Nearly every fragment contributes useful selection or invocation information.

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-argument, fixed-endpoint tool, this supplies nearly everything needed to select and invoke it, including the exact pair, inverse rate, source, price, networks, and authentication expectations. Because there is no output schema, the undocumented response fields and fix-timestamp representation remain notable gaps.

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?

There are no parameters, so there are no undocumented input semantics for the description to explain. The fixed, pair-specific URL reinforces that invocation requires no arguments, meeting the zero-parameter baseline.

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 identifies the exact resource—USD/HUF, its inverse, and the latest ECB reference fix—so the data product is clear despite lacking an explicit retrieval verb. It does not explicitly differentiate itself from other buy_fx_* siblings, although the pair-specific name and URL reduce ambiguity.

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?

An agent can infer that this is appropriate when it needs the latest ECB reference fix for this exact pair and is willing to pay. There is no explicit when-not guidance or routing to alternatives such as buy_fx_eur_huf or buy_fx_usd for different requirements.

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