Skip to main content
Glama

SouthPow crypto & market data

buy_econ_co

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

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

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, the description carries the full burden and largely meets it: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no credentials are needed, that failed calls are not charged, and that values are sourced from the World Bank. It stops short of describing response shape, value freshness/caching, or how payment is actually settled at call time.

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-loading 'Paid.' is excellent structure, and the metrics list is dense and useful. The trailing raw URL and the slightly redundant 'No account, no API key' phrase add little for an agent that already has the tool bound.

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-annotations, no-output-schema tool, the description covers the three things an agent needs: what data comes back, what it costs, and what credentials are not required. Missing are the freshness/date of the World Bank values and any hint about error or partial-result behavior beyond the no-charge-on-failure promise.

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 per the baseline this scores 4; the description appropriately spends its words on scope and cost rather than inventing parameter guidance. Nothing about invocation inputs is left ambiguous.

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 and scope precisely — 'Economic data for country CO' — and enumerates the exact metrics returned (GDP, GDP growth, inflation, unemployment, population, GDP per capita), which is enough to distinguish it from the ~50 sibling buy_econ_* country tools. The only weakness is that the ISO code 'CO' is never expanded to 'Colombia', leaving a small chance of confusion among near-identical 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?

Leading with 'Paid.' plus the exact price gives the agent a real decision signal before calling, and 'No account, no API key' clarifies prerequisites. However, it never states when to prefer this over buy_econ_us/buy_fx_* or what happens if the agent needs a different country or non-World-Bank figures — the usage boundary is implied by the country code alone.

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