Skip to main content
Glama

SouthPow crypto & market data

buy_econ_cn

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 behavioral burden and does well: it discloses paid pricing ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the data vintage (latest World Bank values). It stops short of describing the response payload shape or how payment is executed at call time, which matters for a zero-parameter 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?

Front-loaded with 'Paid.' so the agent immediately knows this is a transactional call, then scope, then payment mechanics, then endpoint URL. Every clause carries information; the only slight inefficiency is the trailing bare URL, which reads as an artifact rather than guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 data comes back at a high level, source, price, chain, and failure policy, which is solid. It lacks the actual return shape (units, currency basis, number of fields) and how the USDC payment is settled during invocation, leaving an agent unable to predict the response or the payment flow.

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 no parameters, so there is no per-argument semantics to add; baseline 4 applies. The description correctly avoids inventing parameter chatter and instead spends its budget on scope and payment terms.

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?

States the exact resource and its scope: economic indicators for country CN (GDP, GDP growth, inflation, unemployment, population, GDP per capita), with the data source named as latest World Bank values. The country code embedded in the name plus the explicit 'for country CN' line separates it cleanly from the dozens of buy_econ_<cc> siblings without opening a schema.

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 implied rather than stated: an agent infers it should call this when it needs China macroeconomic indicators. There is no explicit 'use buy_econ_us for US data' routing statement or when-not condition, though the country-scoped wording does most of the work and the pricing/eligibility notes tell the agent this is a paid call requiring USDC.

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