Skip to main content
Glama

SouthPow crypto & market data

buy_econ_pe

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 handles it well: it discloses the paid nature, the exact price ($0.002 USDC), the accepted payment chains (Base or Solana), that no credentials are needed, and the refund behavior for failed calls. What it omits is the mechanics of how payment is actually settled and whether data is refreshed on each call, which matters for a paid endpoint.

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?

Roughly three sentences, front-loaded with the paid flag and the purpose before pricing and endpoint details. Every clause carries distinct information: content, cost, payment rails, auth, refund policy, URL. No filler or repetition of the tool name.

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?

With zero parameters and no output schema, the description must convey both what is fetched and what comes back, and it handles the field list and the source of truth (latest World Bank values). It does not describe the response shape, units, or date/currency conventions, which is the remaining gap for a data-retrieval tool with no output schema.

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 nothing for the description to disambiguate and the baseline of 4 applies. The country is baked into the tool identity rather than passed as an argument, which the description makes unambiguous.

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?

Names a specific resource (economic data for country PE) and enumerates exactly which indicators are returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The 'PE' country scoping is what distinguishes it from the fifty buy_econ_* siblings, and that scoping is stated in the first clause and reinforced by the endpoint URL.

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?

The opening 'Paid.' plus the price and 'No account, no API key' framing gives an agent clear context for choosing this over unfiltered data sources. It never explicitly says when not to use it or points to the sibling tool for another country, leaving that inference to the country-code convention.

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