Skip to main content
Glama

SouthPow crypto & market data

buy_econ_id

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full behavioral burden and does so well: it discloses the cost ($0.005 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the upstream data provenance (latest World Bank values) plus the endpoint URL. It does not describe the response format or any rate limits, but the economically relevant behavior is disclosed.

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-loaded with the single most decision-relevant fact ('Paid.'), then data content, then price/payment, then failure policy. Every clause is information-dense with no filler; the telegraphic style suits an agent-facing one-liner.

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

Completeness5/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 paid endpoint, the description supplies everything needed to decide and to invoke: data fields covered, source, price, accepted chains, auth requirements, billing-on-failure policy, and the URL. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero-parameter tool, so the baseline is 4, but the phrase 'for country ID' actively invites the misreading that an identifier must be supplied — a real ambiguity given the empty schema. Beyond that the description clarifies the data vintage ('latest World Bank values'), which is useful semantics the schema cannot provide.

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 a specific resource and enumerates the payload exactly (GDP, GDP growth, inflation, unemployment, population, GDP per capita), so an agent knows what data it gets. The weak spot is 'country ID', which reads like an input parameter even though the schema has none and the sibling set encodes the country in the tool name (buy_econ_us, buy_econ_id, etc.) — the country is never stated outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives, despite dozens of near-identical buy_econ_XX siblings. The leading 'Paid.' plus the price does implicitly signal a paid-vs-free choice, but the agent is left to infer that this tool is the Indonesia variant and not a generic country-ID lookup.

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