Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_nzd

Paid. EUR/NZD exchange rate and inverse, latest ECB reference fix. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/eur-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_eur_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 the paid nature, the exact cost ($0.005 USDC), the accepted payment chains (Base or Solana), that failures are not charged, and the upstream data source. It omits rate limits, freshness/cadence, and what the response payload looks like, which keeps it from a 5.

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?

Telegraphic fragments pack purpose, cost, payment rails, prerequisites, and failure policy into a few lines with the core value proposition front-loaded. The raw endpoint URL is somewhat out of place in an agent-facing description but is short and harmless.

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 paid data lookup with no annotations and no output schema, the description covers the essentials an agent needs to commit: what data, what source, what cost, which chains, and that failures are free. Freshness cadence and response shape are the only meaningful gaps.

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 there is no schema semantics to add beyond what already exists; the baseline for a no-param tool applies. The description correctly introduces no parameter concepts that would confuse the caller.

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?

The description names the exact resource (EUR/NZD exchange rate plus its inverse) and the data source (latest ECB reference fix), which separates it cleanly from the hundreds of sibling buy_fx_* pair tools. The purchase action is only implied by 'Paid.' and the price line rather than stated with a verb, so it falls just short of a 5.

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 discloses access prerequisites ('No account, no API key') and the failure policy, which helps an agent decide to call it. However, there is no explicit statement of when to pick this pair tool over a related one (e.g. buy_fx_nzd or buy_fx_eur), leaving routing to the tool name alone.

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