Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_nzd

Paid. USD/NZD 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/usd-nzd.

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

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 well: it discloses that the call is paid, the exact price ($0.002 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits data freshness/latency and return format, but the payment and failure-billing behavior are unusually well 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?

Front-loaded with 'Paid.' then the resource, price, access requirements, and billing policy in terse fragments. Every sentence earns its place except the raw endpoint URL, which is marginally useful but not essential for an agent.

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 single-value lookup with no output schema, the definition covers cost, payment method, access requirements, failure billing, and data provenance. The main missing piece is what the response looks like or how fresh the fix is, which would help an agent decide whether the data fits its need.

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 schema-level to explain. The description correctly signals that no inputs are needed by fixing the pair in the name and describing only payment rails.

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 the specific resource (USD/NZD exchange rate plus its inverse) and the data source (latest ECB reference fix), which is far more than the name alone conveys. It does not explicitly contrast itself with the many sibling pairs (buy_fx_usd, buy_fx_nzd, buy_fx_eur_nzd), but the pair and source are unambiguous.

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 is only implied: the tool name fixes the currency pair and there are no parameters, so an agent knows this is the USD/NZD call. Nothing says when to prefer this over buy_fx_usd or buy_fx_nzd, or how it differs from other FX endpoints, so no explicit routing guidance is present.

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