Skip to main content
Glama

SouthPow crypto & market data

buy_fx_mxn

Paid. Forex rates from MXN 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/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_mxn"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Since no annotations were provided, the description carries the full burden of disclosure. It successfully conveys crucial behavioral traits including the payment requirement, the specific network required for payment, the data source (ECB reference fix), and a failure policy ('Failed calls not charged').

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?

The definition is highly dense, yet every piece of information—pricing, scope, network, source, safety—is front-loaded and necessary, making it maximally efficient.

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

Completeness5/5

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

Given that the tool has zero parameters and no supporting annotations, the description is exceptionally complete. It covers the 'who, what, where, when, and how much' (ECB, MXN, 29 currencies, paid, USDC/Solana) for the agent to interact with it correctly.

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?

With zero parameters and 100% schema coverage, the description's semantic value is high, defining the exact scope and constraints of the data provided (MXN to 29 specific currencies). This high specificity is valuable even without input parameters.

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?

The purpose is stated extremely clearly: providing 'Forex rates from MXN to 29 other currencies.' The combination of the name and description successfully differentiates it from general FX rate tools and sibling coin-buying tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage constraints and policies, such as stating it is 'Paid,' detailing the payment method ('$0.002 USDC on Base or Solana'), and noting safety features like 'No account, no API key.'

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