Skip to main content
Glama

SouthPow crypto & market data

buy_econ_ro

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

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

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 does it well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged, plus the source of the values (latest World Bank data). The remaining gap is the shape of a successful response — with no output schema, an agent still cannot predict the payload structure.

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?

Front-loads 'Paid' — the most consequential fact — then the resource and metric list, then price and rails, then access terms and endpoint. Every sentence adds distinct information; there is no padding despite covering cost, auth, and failure policy.

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, annotation-free tool this covers nearly everything an agent needs before invoking: what data comes back, what it costs, on which chains, whether credentials are needed, and the failure billing rule. The one omission, the response format, matters because no output schema exists to fill it in.

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 no per-argument meaning to add and the baseline of 4 applies. The description correctly implies a fixed country scope rather than implying optional filters an agent might look for.

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 resource precisely (economic data for country RO) and enumerates the returned metrics — GDP, growth, inflation, unemployment, population, GDP per capita — so an agent can separate this from the other 40+ buy_econ_* siblings by country code. The action itself is only implied by the 'buy_' prefix and 'Paid', never stated as an explicit verb, 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?

The country scope implies when the tool applies, but there is no explicit routing guidance — nothing says to prefer buy_econ_ro over buy_fx_eur_ron or buy_pm_recession for Romania-related questions, and no exclusions or prerequisites are stated. Usage is inferable from the country code rather than declared.

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