Skip to main content
Glama

SouthPow crypto & market data

buy_econ_de

Paid. Economic data for country DE: GDP, GDP growth, inflation, unemployment, population, GDP per capita (latest World Bank values). $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/economic/de.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 a good job: it discloses that the call is paid ($0.005 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of explaining how payment is actually settled (wallet, x402-style flow) or any rate limits, which leaves a gap for a paid tool.

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 most decision-relevant fact ("Paid"), then the content, then the price, then the endpoint URL. Telegraphic fragments are appropriate here and no sentence is 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 tool with no output schema and no annotations, the description covers cost, payment rails, failure policy, data source and the metric list. The remaining gap is return shape — nothing says whether values are structured per indicator, what units or reference year they use, or whether history is included versus only the latest snapshot.

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 the country and metric set are fixed by the endpoint rather than configurable, which prevents an agent from hunting for a country or date argument.

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 the exact resource (economic data for country DE) and enumerates the metrics returned — GDP, GDP growth, inflation, unemployment, population, GDP per capita — plus the data source (latest World Bank values). The country code in the description matches the DE suffix, so an agent can distinguish this from the ~50 buy_econ_XX siblings without inspecting schemas.

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 only implied: an agent infers it should call this when it needs German macroeconomic indicators, and the sibling naming convention makes the country alternatives self-evident. There is no explicit when-to-use or when-not-to-use statement, and no mention of related tools (e.g. buy_fx_eur or buy_pm_inflation) that might also serve a macro question.

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