Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_gbp

Paid. USD/GBP 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/usd-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_usd_gbp"
  }
}

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?

No annotations exist, so the description carries the full load, and it does well: price ($0.002 USDC), accepted chains (Base or Solana), no auth required, and failed calls not charged — that last point is genuinely valuable for a paid tool. It omits rate limits and how often the ECB fix refreshes, which matters for a reference-rate product.

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 and front-loaded: lead word 'Paid' sets the commercial constraint before anything else. Every sentence carries a distinct fact (cost, chain, auth, billing on failure, source URL), though the staccato fragments read more like a price tag than prose.

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?

With no output schema and no annotations, the description supplies the commercial and access context an agent needs before spending money. What is missing is the return shape — whether the rate is a number, a string, or an object with both directions — and the fix timestamp.

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?

Zero parameters, so there is nothing to disambiguate and the description correctly spends no words on inputs. The only semantic gap is that 'inverse' is not defined in terms of the returned fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource (USD/GBP exchange rate plus its inverse) and the data source (latest ECB reference fix). Against ~60 sibling buy_fx_* pair tools, the currency pair in the opening clause is what an agent needs to pick this one over buy_fx_eur_gbp or buy_fx_usd_eur.

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?

States eligibility conditions implicitly by saying 'No account, no API key' and 'Paid', but never says when to prefer this pair tool over a sibling like buy_fx_gbp or buy_fx_eur_gbp, nor when a cross-rate would be cheaper than a direct pair. Usage is inferable from the name only.

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