Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_zar

Paid. USD/ZAR 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-zar.

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_zar"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 disclose the traits that matter most for a paid endpoint: price, accepted chains, no auth requirement, and that failed calls are not charged. It omits data freshness details (age of the ECB fix), latency, and response format, but the critical cost and billing semantics are covered.

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?

Fragment-style but front-loaded, with the paid nature and the returned data in the first two sentences; every fragment carries information. The raw endpoint URL is marginal value for an agent that cannot fetch it directly, but it is brief.

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 purchase tool with no output schema, the description covers what is returned (rate and inverse, ECB reference), what it costs, how to pay, and the failure-charge policy. Missing only freshness and response-shape hints, which are minor given the tool's simplicity.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies the pair is fixed and no inputs are needed.

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 concrete verb-plus-resource: the USD/ZAR exchange rate and its inverse from the latest ECB reference fix. The currency pair is explicit, so it is distinguishable from the many buy_fx_* siblings by topic. It does not explain how it differs from buy_fx_zar or buy_fx_eur_zar, leaving sibling disambiguation to the naming pattern.

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?

Gives prerequisites well — paid, $0.01 USDC on Base or Solana, no account or API key — which tells an agent what it needs before calling. However, it never says when to choose this over alternatives such as buy_fx_usd (all USD pairs) or buy_fx_zar, so selection guidance 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