Skip to main content
Glama

SouthPow crypto & market data

buy_econ_br

Paid. Economic data for country BR: GDP, GDP growth, inflation, unemployment, population, GDP per capita (latest World Bank values). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/economic/br.

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

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 well: it discloses that the call costs money, the exact price and payment rails, that no auth is required, that failed calls are not charged (implying safe retry), and that values are 'latest World Bank values' (source and staleness). It omits rate limits, caching behavior, and what a success response looks like.

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?

Four compact fragments, front-loaded with the most decision-relevant fact ("Paid.") followed by contents, price, access requirements, refund policy, and endpoint. Nothing is redundant and nothing is buried.

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 what is returned, where it comes from, what it costs, and how to reach it. Only the response shape and any freshness caveats beyond 'latest' are left unstated, which is minor.

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 is 4. The description correctly implies the country is fixed by the tool itself, which is the only semantic an agent needs here.

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 (economic data for country BR) and enumerates the returned indicators — GDP, GDP growth, inflation, unemployment, population, GDP per capita — so an agent can distinguish it from the buy_econ_XX country siblings and from buy_fx_brl. It lacks an explicit verb ("fetch" / "buy"), relying on the name and the leading "Paid." to convey the action, which keeps it just 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?

Usage is only implied: an agent infers "call this when you need Brazil macro indicators." The description does supply useful preconditions (paid, $0.002 USDC on Base or Solana, no account or API key), but it names no alternative tool and no when-not-to-use condition, e.g. versus buy_fx_brl for currency rates.

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