Skip to main content
Glama

SouthPow crypto & market data

buy_econ_ru

Paid. Economic data for country RU: 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/ru.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 is paid, the exact price ($0.01 USDC), the accepted payment rails, that no account or API key is needed, and that failed calls are not charged. It does not describe the response shape, pagination, or how fresh the 'latest World Bank values' are beyond that phrase.

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' and the resource scope, then packs indicators, price, payment rails, access requirements, failure policy, and endpoint into a few dense sentences with no filler. Every clause carries actionable information.

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 tool with no annotations and no output schema, the description covers purpose, data source, cost, payment, and failure semantics. The only real gap is that with no output schema, the agent gets no hint about the structure of the returned economic data.

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 and there is no schema meaning for the description to add. Nothing is missing on this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (economic data for country RU) and enumerates the exact indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The country code in the description makes it trivially distinguishable from the many buy_econ_* siblings.

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 description establishes the access context (paid, no account or API key, payment on Base or Solana) which implicitly tells the agent this is a purchasable data fetch, but it never states when to choose this over a sibling such as buy_econ_us or buy_crypto_price, nor any exclusions. Usage is inferable from the country scope rather than stated.

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