Skip to main content
Glama

SouthPow crypto & market data

buy_fx_zar

Paid. Forex rates from ZAR to 29 other currencies, 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/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_zar"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full behavioral burden. It does well on cost and access: $0.002 USDC on Base or Solana, no account or API key, and failed calls are not charged, plus the data provenance (ECB reference fix) and endpoint URL. It still omits call mechanics such as freshness/latency, rate limits, payment flow, and what the response looks like.

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?

Extremely compact telegraphic sentences with the paid/cost signal front-loaded, then data scope, then access constraints, then the URL. Every fragment carries information and nothing is padded.

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?

With no annotations and no output schema, the description still covers cost, payment chains, auth, charge policy, and data source, which is enough to call the tool correctly. It could be more complete by describing the returned rate structure or the exact currency list, but the gaps are minor for a zero-parameter endpoint.

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 frames the call as parameterless by fixing both the base currency and the endpoint in the text. Nothing is left for the agent to supply.

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 resource and scope: forex rates with ZAR as the base against 29 other currencies, sourced from the latest ECB reference fix. The ZAR base implicitly separates it from the EUR- and USD-based FX siblings, but it never names a sibling alternative, so differentiation is inferable rather than explicit.

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?

Usage context is implied by the base-currency framing (call this when you need ZAR-quoted rates), and the 'no account, no API key' line removes setup friction. However, there is no explicit when-to-use/when-not-to-use guidance and nothing routing the agent to buy_fx_eur_zar or buy_fx_usd_zar for other bases.

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