Skip to main content
Glama

SouthPow crypto & market data

buy_econ_ch

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

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

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 behavioral burden and does well: cost ($0.01 USDC), accepted chains (Base or Solana), no account/API key, and the no-charge-on-failure policy are all disclosed. It stops short of stating rate limits, response shape, or what happens on partial failure, but the commercial and auth behavior an agent must reason about is present.

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, front-loaded with 'Paid.' so the cost gate is the first thing the agent sees, followed by payload, price, and endpoint. Every sentence adds a decision-relevant fact; nothing is redundant.

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 paid fetch, the description covers what is returned, data vintage (latest World Bank values), cost, payment method, and failure billing. The remaining omission is response format/pagination, which is minor given the small fixed metric set.

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 schema carries nothing to explain; the description correctly signals that the country is hardcoded in the tool rather than parameterized. The 'no account, no API key' note usefully pre-empts an agent looking for credential arguments.

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 concrete resource (economic data for country CH) and enumerates the exact metrics returned, which lets an agent distinguish it from buy_coin_*, buy_fx_*, and buy_tvl_* siblings. It does not spell out that CH = Switzerland or that other buy_econ_* tools cover other countries, but the country code plus the explicit metric list is enough to identify the tool.

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?

The paid nature and payment rails are made explicit, which implicitly frames usage as 'only when the agent is willing to spend $0.01', and 'failed calls not charged' reduces risk. But there is no explicit when-to-use/when-not guidance, no mention of the parallel buy_econ_de/gb/us tools, and no statement about freshness limits or repeat-call caching.

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