Skip to main content
Glama

SouthPow crypto & market data

buy_econ_za

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 disclose the important behavioral traits: cost and payment rails (Base or Solana), no auth requirement, the failure-charging policy, and the data vintage (latest World Bank values). It doesn't mention rate limits, latency, or response shape.

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' and the payload contents, then price, auth, failure policy, and endpoint URL – every sentence carries distinct information. The telegraphic phrasing ('No account, no API key.') is efficient rather than wasteful.

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 paid endpoint, the description covers what it returns, what it costs, how it's paid for, and where it lives. Only the response structure and any usage limits are left unstated.

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?

Zero parameters, so the baseline applies; the description nonetheless adds meaning by noting the values are 'latest World Bank values', which tells the agent about freshness and provenance rather than leaving it to guess.

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 a specific resource (economic data for country ZA) and enumerates the exact metrics returned (GDP, growth, inflation, unemployment, population, GDP per capita, with the data source). The 'ZA' country code is what separates this tool from the roughly fifty buy_econ_XX siblings, and it is stated up front.

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

Usage Guidelines4/5

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

Establishes clear context for deciding whether to call: it is a paid tool, costs $0.002 USDC, requires no account or API key, and failed calls are free. What's absent is explicit routing ('for another country use buy_econ_<CC>') and any statement of when not to use it, but the country-scoped name makes the alternative obvious.

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