Skip to main content
Glama

SouthPow crypto & market data

buy_econ_cz

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

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

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 supplied, the description carries the full behavioral burden and does well: it discloses cost ($0.002 USDC), accepted payment rails (Base or Solana), that no account or API key is needed, and the failure-billing policy. What it omits is the response shape/format and any freshness caveat beyond 'latest World Bank values', which for a paid data call would be helpful.

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?

The cost qualifier 'Paid.' is front-loaded where it matters most, followed by data coverage, then payment/auth/failure terms and the raw endpoint URL. It is a single dense telegraphic sentence with no filler, though the trailing bare URL fragment is slightly abrupt and could be labeled as an endpoint rather than just 'URL'.

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, no-annotation tool, the description covers the things an agent actually needs: what data, what it costs, how to pay, that no credentials exist, and that failures are free. The remaining gap is that the return format and whether values are cached or freshly sourced are unstated, but this is minor given the simplicity of the call.

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 input schema is empty with zero parameters, so the baseline is 4. The description usefully explains why no arguments are required — country and metrics are baked into the endpoint, and 'No account, no API key' preempts the natural question of whether auth parameters are needed.

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 resource precisely (economic data for country CZ) and enumerates the exact metrics returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. It implicitly distinguishes itself from the ~50 sibling buy_econ_<cc> tools via the CZ country code, though it never spells out 'Czech Republic' and there is no explicit action verb (e.g., 'fetch'), so an agent must infer that the call simply retrieves the bundle.

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?

Leading with 'Paid.' plus the exact $0.002 price and 'Failed calls not charged' gives an agent the cost context needed to decide whether a paid call is warranted. However, it never states when to prefer this over a free alternative, nor does it mention related paid siblings such as buy_fx_czk or buy_econ_us that might be confused with it, so usage is only implied by the data-coverage list.

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