Skip to main content
Glama

SouthPow crypto & market data

buy_fx_eur_brl

Paid. EUR/BRL 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-brl.

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

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, the description carries the full burden and does a surprisingly good job: it discloses price ($0.005 USDC), payment rails (Base or Solana), zero auth requirement, a failure policy (failed calls not charged), and the underlying data source (ECB reference fix) which implies daily-ish freshness. It omits rate limits, latency, and caching behavior.

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 fragments, each carrying distinct information: cost flag, data description, pricing, auth, failure policy, endpoint. 'Paid.' is front-loaded so an agent sees the billing status before anything else. No sentence is redundant with another.

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 description covers cost, payment, auth, failure handling, and source. The one genuine gap is return shape: with no output schema, the agent is not told what fields come back (rate, inverse, timestamp) or the precision/format to expect.

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 the baseline of 4 applies. There is nothing for the description to clarify about inputs, and it does not waste words on nonexistent options.

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?

Names the exact resource and scope: the EUR/BRL pair, both directions (rate and inverse), sourced from the latest ECB reference fix. That is far more specific than the bare tool name. It never routes the agent away from near-duplicate siblings such as buy_fx_eur, buy_fx_brl, or buy_fx_usd_brl, so trimming one point is appropriate despite the strong verb-and-resource phrasing.

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 gives prerequisites (paid, needs USDC on Base or Solana, no account or API key), which tells the agent whether it can call it. It never says when to prefer this over the EUR-base or USD-base sibling series, or whether a EUR->BRL cross should be derived from buy_fx_eur instead. Usage guidance is implied rather than explicit.

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