Skip to main content
Glama

SouthPow crypto & market data

buy_econ_tw

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 so well for the commercial aspects: price ($0.005 USDC), accepted chains (Base or Solana), no account/API key required, and 'Failed calls not charged' clarifies billing on error. It stops short of describing response shape or latency, which matters since there is no output schema.

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 'Paid.' so cost is the first thing the agent sees, then content, then price/rails, then auth/error terms. Every sentence is a distinct actionable fact with no filler or repetition 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, single-resource paid data endpoint, the description covers what data, freshness (latest World Bank values), cost, payment rails, and failure billing. The one real gap is the absence of any hint about return format, which is unaddressed because no output schema exists.

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 and the input schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; the country and indicator scope are baked into the description rather than parameters, which is appropriate.

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?

States a specific resource (economic data for country TW) and enumerates the exact indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The 'TW' suffix plus the explicit country mention separates it cleanly from the many buy_econ_* siblings without needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear selection context: paid macro data for Taiwan, sourced from latest World Bank values, and 'Paid.' up front signals it is not a free call. It does not state exclusions or route to alternatives (e.g. other country tools or free data sources), but for a single-country endpoint the alternative set is obvious from the sibling naming.

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