Skip to main content
Glama

SouthPow crypto & market data

buy_econ_pl

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

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

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 carries the full burden and does unusually well: it discloses cost ($0.002 USDC), accepted payment rails (Base or Solana), the absence of any account or API key requirement, and the failure policy ('failed calls not charged'). What is missing is only secondary behavior such as response shape, latency, or caching/refresh cadence of the World Bank values.

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?

The description is front-loaded with 'Paid.' then the payload, then the price/rails, then the terms, then the endpoint URL — each fragment carries distinct decision-relevant information. There is no filler, repetition, or restatement of the tool name.

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 substitutes well for a return schema by enumerating the six metrics and naming the underlying data source and freshness. It stops short of describing units, currency basis, or the response envelope, which would matter for an agent parsing the result.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameters and instead spends its space on what the call returns and costs.

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 the resource precisely: economic data for country PL, with an explicit enumeration of the metrics returned (GDP, growth, inflation, unemployment, population, GDP per capita) and the source (latest World Bank values). The country code plus the metric list lets an agent distinguish it from the other buy_econ_* siblings, though it never explicitly says 'this is the Poland variant, use buy_econ_us for the US'.

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 agent learns this is a paid, no-signup way to get Polish macro data, and the price point helps it decide whether the call is worth it. However, there is no explicit when-to-use/when-not guidance and no routing to alternatives such as buy_econ_us or buy_fx_pln for related data.

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