Skip to main content
Glama

SouthPow crypto & market data

buy_fx_cad

Paid. Forex rates from CAD 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/cad.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses cost ($0.002 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the data provenance (ECB reference fix). It does not state rate limits, update cadence for the fix, or what the successful response looks like, which is a real gap for a paid call.

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?

Front-loaded with 'Paid.' so cost is the first thing the agent sees, then scope, price, payment rails, and the endpoint — five short clauses, none redundant. Nothing could be cut without losing a distinct fact.

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, no-output-schema fetch, the description covers cost, payment method, auth requirement, failure billing policy, data source, and endpoint URL. The remaining gap is response shape (quote key, timestamp/precision), which matters because no output schema exists to describe it.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The '29 other currencies' and 'CAD' framing usefully communicates the fixed input without needing arguments.

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 states a specific verb and resource: 'Forex rates from CAD to 29 other currencies, latest ECB reference fix.' The base currency and source pin down scope against the many sibling buy_fx_* tools, though it never names an alternative (e.g. buy_fx_usd_cad for the inverse pair), so an agent must infer the distinction from the name alone.

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 implied through the base currency (CAD) and the '29 other currencies' scope, so an agent can tell whether it needs CAD-based rates. However, there is no explicit when-to-use/when-not guidance and no routing to sibling FX tools for other base currencies or for cross-pairs.

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