Skip to main content
Glama

SouthPow crypto & market data

buy_econ_pt

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

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

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 usefully discloses the financial side effect, exact $0.005 price, USDC payment on Base or Solana, lack of account or API-key requirements, and that failed calls are not charged. Source and freshness context are also supplied, though payment authorization or settlement mechanics are not explained.

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 compact and front-loads the paid nature and dataset scope before payment and authentication details. Each short statement adds useful information, and the endpoint URL is placed last without disrupting readability.

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 lookup, the description provides enough scope, source, cost, and prerequisite information to select and invoke it confidently. Because there is no output schema, the absence of response format, indicator units, and metric-specific reference periods remains a noticeable gap.

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?

There are no parameters, so the baseline is 4. The fixed country scope and country-specific URL reinforce that the agent need not supply a country code, date range, or indicator selection.

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 identifies a fixed economic dataset for country code PT and enumerates six indicators, distinguishing it from the other country-specific buy_econ_* siblings. It also names World Bank as the source, although the retrieval action is only implicit and PT is not expanded to Portugal.

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 stated scope implies using this tool for latest Portuguese macroeconomic indicators rather than the coin, FX, or other data tools. However, it gives no explicit when-to-use or when-not guidance and does not direct agents to another buy_econ_* sibling when a different country is required.

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