Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_aud

Paid. EUR/AUD 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-aud.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description discloses substantial operational behavior: the call is paid, costs $0.002 USDC, supports Base or Solana, requires no account or API key, and does not charge for failed calls. It also provides the endpoint and data provenance, but leaves payment/network selection and the ECB publication cadence unexplained.

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?

The description is compact and front-loads the paid nature and exact resource, followed by price, authentication requirements, failure charging, and URL. Each statement contributes useful selection or invocation information without filler.

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-argument paid lookup, nearly all essential invocation information is present despite the absence of annotations and an output schema. Details about response fields or as-of timestamps, ECB fix timing, and how the caller chooses Base versus Solana would make it more complete.

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 has zero parameters, so the baseline score of 4 applies. The fixed endpoint and currency pair mean there are no input choices or formats requiring further explanation.

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 identifies the exact data product: the EUR/AUD rate, its inverse, and the latest ECB reference fix. This distinguishes it by currency pair and source from the other FX siblings, although it lacks an explicit retrieval verb such as 'get' or 'fetch'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Specifying the currency pair and ECB reference fix gives clear context for selecting this tool when that reference rate is needed. It does not explicitly contrast it with siblings such as buy_fx_aud or buy_fx_usd_aud, nor clarify that an ECB fix should not be treated as a live trading quote.

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