Skip to main content
Glama

SouthPow crypto & market data

buy_econ_cl

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

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

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, the description carries the full burden and does well: it discloses that the call is paid ($0.002 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. What it omits is the response shape and data vintage/units, which matters because 'latest World Bank values' can lag by a year or more.

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-loads the two facts an agent needs first ('Paid.'), then scope, then pricing/access terms, then the URL in a single tight paragraph. Every sentence adds information; nothing is redundant with the empty schema.

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-param, no-output-schema endpoint this covers purpose, cost, payment rails, auth requirements, failure billing, and endpoint URL — an agent can call it without further research. The remaining gap is that with no output schema, the return format (field names, units, currency) is entirely undisclosed.

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 the baseline is 4. The description correctly implies no inputs are required by stating the country and metric set are fixed in the endpoint itself.

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?

States a specific resource and enumerates the exact metrics returned (GDP, growth, inflation, unemployment, population, GDP per capita) sourced from the World Bank. The country is only given as the code 'CL', so the agent must map that to Chile, and there is no prose distinguishing it from the ~45 sibling buy_econ_XX endpoints beyond the suffix.

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 scope ('latest World Bank values' tells the agent there is no historical/date selection), but the description never says when to pick this over alternatives such as buy_fetch_* or buy_pm_inflation, nor what to do if the country is wrong. Acceptable for a zero-param endpoint, but guidance is inferred rather than stated.

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