Skip to main content
Glama

SouthPow crypto & market data

buy_econ_th

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 substantial work: it discloses that the call is paid, the exact price ($0.005 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and the upstream data source. What is missing is any statement of response shape, rate limits, or freshness lag beyond 'latest'.

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 dense and front-loaded: cost and payment terms, then the data payload, then access requirements, then the endpoint. Nearly every clause carries information an agent needs before paying; the trailing raw URL is the only element of marginal value since the tool is already addressable by 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, no-annotation paid endpoint, the description covers the essentials: what data comes back, where it comes from, what it costs, how to pay, and that failures are free. The remaining gap is response format and freshness granularity, which matters somewhat for an economic-indicator tool but is not blocking.

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 baseline is 4 and there is nothing for the description to disambiguate. The country is baked into the endpoint, which the description makes explicit via the TH label and the URL.

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 a specific resource and scope ('Economic data for country TH') and enumerates the exact indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The 'TH' country code in both name and text makes the distinction from siblings like buy_econ_us or buy_econ_vn unambiguous, though it never states that routing rule explicitly.

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?

'Paid.' front-loads the cost consideration and the 'No account, no API key' line tells the agent there is no setup, which is genuine usage context. However, there is no when-to-use/when-not guidance, no mention of when to prefer buy_fx_thb or buy_pm_* for related Thai economic signals, and no statement about data staleness beyond 'latest World Bank values'.

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