Skip to main content
Glama

SouthPow crypto & market data

buy_econ_sa

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description does the heavy lifting: it discloses cost ($0.002 USDC), accepted chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and that values are latest World Bank figures. That is real behavioral context beyond the schema. It stops short of response shape or pagination/freshness cadence, which matters for a paid call.

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 token ('Paid.'), then payload, then price, then terms, then endpoint. Every clause earns its place and nothing is padded.

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-argument, no-output-schema paid data tool, an agent learns what it gets (six named metrics, World Bank source), what it costs, how it pays, and what happens on failure. The remaining gap is the 'SA' abbreviation, which an agent could confuse with South Africa given the buy_econ_za sibling.

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 schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals that no inputs are needed, since the country and metric set are fixed by the endpoint.

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 gives a concrete resource with an itemized payload: 'Economic data for country SA: GDP, GDP growth, inflation, unemployment, population, GDP per capita (latest World Bank values).' An agent can tell it apart from buy_coin_*, buy_fx_*, or buy_yields_* siblings. The one weakness is that 'SA' is never spelled out as Saudi Arabia, which is genuinely ambiguous next to the buy_econ_za (South Africa) sibling.

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 by the country-tagged name plus the field list, and the lead word 'Paid.' signals this is not a free lookup. However, there is no explicit when-to-use vs. when-not guidance and no routing advice to the many adjacent buy_econ_* country tools or to buy_search when a different country is needed.

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