Skip to main content
Glama

SouthPow crypto & market data

buy_econ_at

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does it well: it discloses cost ($0.002 USDC), accepted chains (Base or Solana), that no account or API key is needed, and critically that failed calls are not charged — a key risk fact for an agent deciding to spend. The remaining gap is that it never describes the response shape (units, currency basis, per-metric fields) for a tool with no output schema.

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?

It is front-loaded with the single most decision-relevant token ("Paid."), then the resource, then the metrics, then the payment mechanics. Nearly every clause carries information, though the raw endpoint URL at the end is marginal for an agent that will invoke via the tool interface.

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 tool, the description covers purpose, data source, recency, price, payment rails, and failure billing — enough to call it confidently. It stops short of describing the returned payload structure (field names, currency, period format), which is the one thing an agent cannot learn from the empty 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 zero parameters, so there is nothing for the description to disambiguate; the country and metric scope are baked into the endpoint. Baseline 4 applies, and the description adds the useful constraint that values are the latest World Bank figures rather than real-time data.

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?

The description names a specific resource (economic data for country AT) and enumerates the exact metrics returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The ISO country code in the text matches the sibling naming convention (buy_econ_us, buy_econ_de), so an agent can distinguish this from the other ~50 country variants without opening a schema.

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 context is implied rather than stated: the leading "Paid." plus the price signals this is a paid alternative to free tools, and "No account, no API key" removes a common blocker. However, there is no explicit when-to-use or when-not-to-use guidance and no sibling is named as an alternative (e.g. buy_econ_us for US data), so the agent must infer selection from the country code alone.

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