Skip to main content
Glama

SouthPow crypto & market data

buy_econ_gr

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 burden and does well: it discloses that the call is paid ($0.005 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits and the response format, but covers the cost/auth/failure profile an agent needs before spending money.

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?

Roughly three dense sentences with no filler; the cost signal ('Paid.') is front-loaded so an agent sees the spend implication first. The trailing bare URL is slightly awkward but is one of the most useful facts for an agent deciding whether to spend.

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 purchase tool, the definition covers resource identity, data provenance, cost, payment rails, auth requirements, and failure pricing — everything needed to decide and invoke. The only genuine gap is the response payload shape (JSON fields, units, currency of GDP), which cannot be inferred from the schema since none 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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The enumerated metric list usefully signals what the no-arg call returns, which is the only meaningful 'parameter-like' information available.

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?

Names a specific resource (economic data for country GR) and enumerates exactly which metrics are returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The 'GR' suffix plus the country code in prose makes it trivially distinguishable from the ~50 sibling buy_econ_* country tools.

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?

Implies usage context via 'latest World Bank values' (i.e., current snapshot, not historical series) and states payment prerequisites, but never explicitly says when to choose this over a currency (buy_fx_*) or prediction-market (buy_pm_inflation) sibling for macro data. Usage is inferable rather than stated.

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