Skip to main content
Glama

SouthPow crypto & market data

buy_fx_brl

Paid. Forex rates from BRL to 29 other currencies, latest ECB reference fix. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/forex-rates/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_brl"
  }
}

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, the description carries the full burden and does real work: it discloses the paid nature, the exact price and accepted payment chains, that no credentials are needed, and that failed calls are not charged. It also names the data source and freshness (latest ECB reference fix). The one gap is that it never explains how the payment itself is executed, which matters for a purchase tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact and front-loaded: 'Paid.' leads, then what the data is, then cost, rails, auth, failure policy, and endpoint. Every sentence carries a distinct fact with no repetition, though the raw URL in prose is slightly out of place versus the rest of the framing.

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-param tool with no annotations and no output schema, the description is largely self-sufficient: cost, access model, billing policy, and data provenance are all present. What is missing is a hint at the response shape (the rate list format) and how the USDC payment step is triggered, which an agent must still discover at call time.

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?

Zero parameters, so the baseline is 4 and the schema cannot add anything. The description still usefully clarifies that the base is fixed at BRL and the tool returns 29 target currencies, which is meaningful semantic framing beyond an 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?

States a specific resource and scope: BRL-denominated forex rates covering 29 other currencies from the ECB reference fix. It implicitly separates this from pair-specific siblings like buy_fx_eur_brl or buy_fx_usd_brl by declaring a BRL base with 29 targets, but never names those alternatives outright.

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?

Provides the prerequisites for calling it (paid, $0.01 USDC on Base or Solana, no account or API key) which is useful pre-call context. However there is no guidance on when to choose this multi-currency BRL base versus the many pairwise fx siblings, so the routing decision is left to inference.

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