Skip to main content
Glama

SouthPow crypto & market data

buy_econ_pk

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

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

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, the description carries the full burden and does well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of describing the response payload shape, data freshness beyond 'latest World Bank values', or any rate limits.

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?

The description is short, front-loaded with 'Paid.', and every clause carries information: data scope, price, payment rails, auth model, failure policy. The trailing raw endpoint URL is the one element of marginal value to an agent that already has the tool binding, but it does not bloat the text.

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 definition covers what an agent needs to decide and pay: the metric list, the data source, the price, the payment chains, and the failure policy. The main gap is the shape of the returned payload, which no output schema documents and the description only sketches via the metric names.

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 and the baseline of 4 applies. No parameter meaning is lost because none exist.

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 the specific resource (economic data for country PK) and enumerates the exact fields returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The 'PK' country code plus the explicit metric list distinguishes it from the large family of buy_econ_* siblings without needing to open any 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 is implied by the country scope but never stated: there is no explicit 'use this for Pakistan, use buy_econ_us for the US' routing, and no guidance on when this paid source is preferable to a free alternative. The payment prerequisites ('$0.01 USDC on Base or Solana', 'No account, no API key') give useful pre-call context but are not when-to-use guidance.

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