Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_zar

Paid. EUR/ZAR 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-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_eur_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 full burden and does well: it discloses cost ($0.002 USDC), accepted payment chains (Base or Solana), no auth requirement, and the failure policy ('Failed calls not charged'). It also names the underlying data source and its recency ('latest ECB reference fix'), which is meaningful behavioral context. It does not state refresh cadence or response shape.

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-loaded with the key qualifier ('Paid'), then purpose, price, access conditions and endpoint URL in tight fragments. Every element is informative; the raw URL at the end is the only mildly extraneous item for an agent that never calls it directly.

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, no-output-schema tool this covers the essentials: what is returned, where the data comes from, what it costs, how to pay, and that failures are free. The main remaining gap is the concrete shape/format of the returned rate object, which no output schema supplies.

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 and there is nothing for the description to compensate for. It correctly implies a parameterless call and notes both the rate and its inverse are returned.

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?

Names the specific resource (EUR/ZAR exchange rate), states it returns the inverse as well, and identifies the data source (latest ECB reference fix). An agent can distinguish it from buy_fx_usd_zar or buy_fx_zar by the currency pair in the name, though the description never explicitly routes to those siblings.

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?

Implied usage is clear from the currency pair, and the payment/auth conditions are stated ('Paid', '$0.002 USDC on Base or Solana', 'No account, no API key'). However there is no explicit when-to-use vs when-not guidance and no pointer to the equivalent sibling tools for other pairs or the inverse direction.

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