Skip to main content
Glama

SouthPow crypto & market data

buy_fx_gbp

Paid. Forex rates from GBP 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/gbp.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does a lot: it discloses cost, accepted payment chains (Base or Solana), that no auth is required, that failed calls are not charged, and the upstream data source (ECB reference fix). What it omits is rate limits, freshness/update cadence, and whether the payment is per-call settled up front.

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: payment status first, then what it returns, then cost and auth, then the URL. The telegraphic fragment style ('Paid. ... No account, no API key.') is efficient, though the raw URL and some numeric detail could be considered tail information rather than core.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no annotations and no output schema, the description should also hint at the response shape (whether it returns a rate map keyed by currency, precision, timestamp of the fix). It covers source and coverage well but leaves the return format entirely unspecified.

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; there is no argument meaning to clarify. The description usefully confirms no credentials or account identifiers are needed, which reinforces that the call is argument-free.

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 concrete resource and direction: 'Forex rates from GBP to 29 other currencies' with the data source declared as 'latest ECB reference fix'. An agent can tell this is the GBP-base variant rather than the many cross-rate siblings, though it never names those siblings explicitly (e.g., buy_fx_eur_gbp, buy_fx_usd_gbp) so the routing is inferred from the base currency 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?

Gives strong operational context for calling it (paid, $0.002 USDC, no account/API key needed, failures not charged) and even the endpoint URL, but there is no explicit when-to-use or when-not-to-use guidance relative to the ~40 other buy_fx_* tools. Usage is implied by the GBP base rather than directed.

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