Skip to main content
Glama

SouthPow crypto & market data

buy_econ_es

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

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

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 that the call is paid ($0.002 USDC on Base or Solana), that no account or API key is required, and — importantly for an agent weighing risk — that failed calls are not charged. Missing are the response shape, data freshness beyond "latest World Bank values", and any rate limits, which keeps it from a 5.

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 four short sentences, each carrying distinct information: paid status, data contents, payment/auth terms, and endpoint URL. The cost and no-account terms are front-loaded where an agent evaluating whether to call will see them first, and there is no filler.

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 lookup tool, the definition covers what the agent needs to decide and to call: the country, the metric list, the price, the payment rails, the lack of auth, and the failure-billing policy. Only the response format and data vintage semantics remain 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?

The tool takes no parameters and the schema is empty at 100% coverage, so the baseline is 4. The description correctly adds no parameter prose because none is needed, and it instead spends the space on the metric list and payment terms.

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 (economic data for country ES) and enumerates the exact metrics returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita, sourced from the World Bank. It distinguishes this tool from the 48 sibling country tools only through the ISO code "ES" in the first sentence; it never spells out "Spain" or tells the agent that sibling country tools exist. There is also no explicit verb ("fetch"/"return"), only a noun phrase introduced by "Paid.".

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 rather than stated: an agent can infer this is the tool for Spanish macroeconomic indicators and that the metric list defines its scope. However, nothing tells the agent when to prefer it over adjacent tools such as buy_fx_eur (currency rates) or other buy_econ_* country variants, and there are no prerequisites or exclusions spelled out.

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