Skip to main content
Glama

SouthPow crypto & market data

buy_fx_usd_mxn

Paid. USD/MXN 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-mxn.

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

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 supplied, the description carries the full burden and does well: it discloses cost, accepted payment rails, that no credentials are required, and that failures are not billed. It stops short of explaining the actual payment handshake (e.g. x402 flow), response shape, or refresh cadence beyond 'latest ECB reference fix'.

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?

Extremely front-loaded: payment status first, then the data, then price and rails, then billing behavior, then endpoint. Every clause carries distinct information for an agent deciding whether and how to call. The embedded URL is unusual but functional for a paid endpoint.

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 tool, the definition covers what is being bought, its source, its cost, and its billing guarantees. The remaining gap is that the response contents (rate fields, inverse, timestamp) are only gestured at via 'and inverse' rather than described.

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?

There are zero input parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly presents the tool as parameterless, implicitly telling the agent not to construct 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 names the exact resource ('USD/MXN exchange rate and inverse') and the data provenance ('latest ECB reference fix'), which is far more specific than the bare name. It distinguishes the pair implicitly, but never contrasts itself with the adjacent siblings like buy_fx_mxn or buy_fx_usd_eur, so an agent must infer the pairing 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?

It states payment terms ('Paid.', '$0.002 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged'), which tells the agent the preconditions for calling. However, there is no when-to-use or when-not-to-use guidance relative to the dozens of other buy_fx_* tools, and no statement that this is a once-daily ECB fix rather than an intraday quote.

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