Skip to main content
Glama

SouthPow crypto & market data

buy_econ_nz

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full load and does well: it discloses cost, accepted chains, the absence of auth, the failure-billing policy, and the endpoint URL. It stops short of describing rate limits, latency, or the shape/units of the returned payload.

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?

Front-loaded with 'Paid.' and then the subject matter, with short factual sentences and no filler. Minor redundancy between 'Paid.' and the explicit price, and 'No account, no API key' restates the same idea twice.

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 this covers the essentials an agent needs to decide and pay: what data, what source, what cost, what chain, what auth. It does not indicate the response structure or whether values are nominal vs. per-capita units, which would be the remaining useful addition.

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 clarify beyond what the empty schema already states. Baseline of 4 applies.

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 (economic data for country NZ) and enumerates the exact indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. It also pins the source and recency ('latest World Bank values'), so an agent can distinguish it from buy_econ_au/buy_econ_us and from buy_fx_nzd 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 Guidelines4/5

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

It clearly frames this as a paid call ($0.01 USDC on Base or Solana) with no account or API key needed and no charge on failure, which is exactly the context an agent needs before committing. It gives no explicit when-not-to-use guidance or pointers to sibling country/fx tools, so routing is left partly to inference.

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