Skip to main content
Glama

SouthPow crypto & market data

buy_fx_nzd

Paid. Forex rates from NZD 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/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_nzd"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so well: it discloses the paid model, exact price, accepted chains, that no account or API key is required, that failed calls are not charged, and the upstream data source and freshness ('latest ECB reference fix'). Those are exactly the operational facts an agent needs before spending money on a call.

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?

Very compact and front-loaded with the payment fact first, then the data description, then access terms, then the URL. The telegraphic style ('Paid.' as a standalone fragment) is slightly terse, but no sentence is redundant.

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, annotation-free, output-schema-free tool, the description covers cost, chains, auth, failure charging, and data provenance. The only meaningful gap is the shape of the returned payload (per-currency rate list format), which an agent must discover on the first paid call.

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 no parameters, so there is nothing for the description to disambiguate; the implicit 'NZD to 29 other currencies' framing confirms the output is a fixed basket with no caller-supplied input. Baseline 4 applies for a zero-parameter tool.

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: ECB reference forex rates from NZD to 29 other currencies. The base currency is unambiguous, which implicitly separates it from buy_fx_usd / buy_fx_eur and from the cross-rate siblings like buy_fx_usd_nzd, but the description never explicitly names an alternative, so the differentiation is inferred rather than stated.

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?

It gives strong access/payment context ('$0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged.') but no when-to-use guidance relative to the ~40 other buy_fx_* tools. An agent looking for a USD/NZD or EUR/NZD quote must deduce the correct sibling from the name alone; nothing says 'use buy_fx_eur_nzd instead if your base is EUR'.

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