Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur

Paid. Forex rates from EUR to 29 other currencies, latest ECB reference fix. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/eur.

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

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 at all, the description carries the full burden and does substantial work: it declares the tool is paid, the exact price ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and the data source/endpoint. What it omits is freshness/latency and whether the charge is per call or per successful response beyond the failure clause.

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?

Six short fragments, front-loaded with the critical fact ("Paid.") followed immediately by what you get. Every clause adds a decision-relevant fact (cost, chain, auth, failure policy, source); the bare URL at the end is slightly abrupt but practically useful for direct HTTP invocation.

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-param, no-output-schema tool, the description covers the things an agent cannot get from structured fields: cost, payment rails, auth requirements, charge policy on failure, and data provenance. The main gap is the shape of the returned rate set, which the agent must discover at runtime since no output schema exists.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly signals a no-argument call by specifying the base currency as fixed (EUR) rather than as an input.

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?

"Forex rates from EUR to 29 other currencies, latest ECB reference fix" states a specific verb (retrieve rates), resource (EUR forex), and scope (all 29 quotes, ECB fix). It distinguishes itself from the many pair-specific siblings like buy_fx_eur_jpy by saying it returns the whole basket, though it never names those siblings explicitly.

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 by scope: an agent can infer this is the right call when it wants EUR against everything at once. There is no explicit "use X instead when you need a single pair" routing against the large buy_fx_eur_* family, so the selection logic is left to inference.

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