Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_cad

Paid. USD/CAD 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-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_usd_cad"
  }
}

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 supplied, the description carries the full burden and does a lot of work: it discloses the paid nature, the exact price, the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. What remains undisclosed is the response shape and how the payment is transacted (e.g., whether the call returns a 402 challenge first), which is significant for a payment-gated tool.

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?

Roughly thirty words of telegraphic, front-loaded text: cost and payment rails first, then access requirements, then failure policy, then the endpoint. Every fragment conveys a distinct fact an agent needs, with no 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-parameter, no-output-schema paid data fetch, the definition covers pricing, payment chains, authentication, and failure charging — the details that actually gate correct invocation. It falls short only on how payment is settled and what the payload contains, which an agent must discover at runtime.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so the description cannot add parameter meaning and the baseline is a 4. However, the trailing raw endpoint URL is the only technical detail added and it does not clarify invocation, so it adds little over the empty schema.

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 names the exact resource (USD/CAD exchange rate plus its inverse) and the data source (latest ECB reference fix), which is enough to distinguish it from the many buy_fx_* siblings keyed on other currency pairs. The action verb is only implied by the 'buy_' prefix and the '$0.002' price line rather than stated outright, which keeps it just short of a 5.

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: an agent can infer it should call this when it needs the USD/CAD reference rate, and the price line implies 'only pay when you actually need this pair.' There is no explicit statement of when to prefer this over buy_fx_cad or buy_fx_usd, and no guidance on caching or freshness expectations.

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