Skip to main content
Glama

SouthPow crypto & market data

buy_econ_au

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/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 a decent job: it discloses that the call is paid ($0.005 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and that values come from the World Bank. It does not state rate limits, latency, response shape, or how stale the 'latest' World Bank values may be, which are the remaining behavioral unknowns for a paid endpoint.

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 payment status is front-loaded in a single word ('Paid.'), followed by scope, price and rails, access requirements, billing policy, and endpoint. Every clause carries distinct information and nothing is repeated from structured fields.

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, the description supplies what matters: the data source, the indicator set, the cost, the payment networks, and the failure-billing policy. Only the response format and data freshness are left unspecified, which is a minor gap rather than a blocking one.

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 disambiguate; the baseline of 4 applies. The description correctly implies a fixed, country-scoped request with no filtering options.

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 the resource precisely (economic data for country AU) and enumerates the exact indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. An agent can immediately tell this apart from the buy_econ_* siblings for other countries and from buy_fx_aud. It stops short of an explicit verb or a stated exclusion versus the FX tools, so it is clear but not fully differentiated in prose.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative such as buy_fx_aud for exchange rates or buy_econ_us for the US variant. Usage is only implied by the country code and the indicator list, leaving the agent to infer selection from the tool name.

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