Skip to main content
Glama

SouthPow crypto & market data

buy_econ_jp

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 the cost ($0.002 USDC), the accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the data provenance (latest World Bank values). It stops short of describing response shape or how stale 'latest' values may be.

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?

It is dense and front-loaded — 'Paid.' sets the commercial framing immediately, then data scope, then price, then access conditions, then endpoint. No sentence is wasted for a zero-parameter tool.

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 tool with no output schema and no annotations, the definition covers everything needed to decide and invoke: data contents, source, price, payment rails, and failure billing policy. Only the return format and data freshness remain unspecified.

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 zero parameters, so the baseline is 4. The description adds useful meaning by specifying exactly which indicators the fixed endpoint returns instead of just naming the country.

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 resource precisely (economic data for country JP) and enumerates the indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. Combined with the tool name's country suffix, an agent can distinguish this from the other buy_econ_* country variants without opening 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 Guidelines3/5

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

It implies the usage context (Japan macro indicators, latest World Bank values) and gives purchase preconditions: paid, no account, no API key. However, it never states when to prefer this over a sibling such as buy_fx_jpy or another buy_econ_* country tool, and there are no exclusions.

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