Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_mxn

Paid. EUR/MXN exchange rate and inverse, latest ECB reference fix. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/eur-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_eur_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 handles it well: it discloses cost ($0.005 USDC), accepted chains (Base or Solana), payment model (paid upfront, failed calls not charged), lack of auth requirements, data provenance (ECB reference fix), and the endpoint. What it omits is the response shape (e.g. timestamp, freshness) and the fact there is no output schema, so the agent cannot know the return payload's structure from the description.

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?

Six short clauses, front-loaded with the payment status and the data itself, then cost, prerequisites, and endpoint. No sentence is padding, and the telegraphic style suits a machine-read tool definition.

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 the essentials an agent needs to commit: what data, what it costs, how to pay, and that failures are free. The remaining gap is the return value — no output schema exists and the description only gestures at 'rate and inverse' without saying how they are delivered.

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, so there is nothing for the schema to document and nothing for the description to add. The description correctly implies the pair is fixed by the tool rather than configurable. A 5 would require nothing more, but there is no positive parameter information to reward.

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 a specific resource and scope: the EUR/MXN pair, both directions (rate and inverse), sourced from the latest ECB reference fix. That distinguishes it from most siblings by currency pair. It does not explicitly state why an agent would pick this over the closely related buy_fx_mxn or buy_fx_eur, which keeps it 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?

Usable context is implied by the pair name, and the payment terms ('$0.005 USDC on Base or Solana', 'no account') tell the agent what it must have ready. There is no explicit when-to-use or when-not-to-use statement, and no routing to alternatives such as the other fx siblings, so the agent must infer the choice.

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