Skip to main content
Glama

SouthPow crypto & market data

buy_econ_il

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

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

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, the description carries the full burden and does a solid job: it discloses the paid model ($0.01 USDC), accepted chains (Base or Solana), no account/API key requirement, and that failed calls are not charged — all non-obvious behavioral facts an agent needs before spending money. It stops short of describing latency, response format, or whether repeated calls re-charge.

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?

It is telegraphic and front-loaded — 'Paid.' is the first token, followed by what you get, then price, then payment mechanics. Every clause carries information, though the raw endpoint URL is of marginal use to an agent and the indicator list could be tightened.

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?

With no output schema and no annotations, the description must convey both content and cost, and it does: it lists the returned indicators, their source (World Bank) and recency (latest values), plus the payment terms. The main remaining gap is the shape of the response payload (field names, units, reference year), which an agent must discover by calling.

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; baseline is 4. The description correctly signals that country and indicator set are fixed rather than configurable.

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 IL — and enumerates the exact indicators returned (GDP, GDP growth, inflation, unemployment, population, GDP per capita). The country code in the name plus 'country IL' in the text distinguishes it from the ~50 sibling buy_econ_XX tools, though it never explicitly says siblings cover other countries.

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?

Usage is only implied: an agent can infer it should call this when it needs Israeli macroeconomic figures, and that other buy_econ_* tools cover other countries. There is no explicit when-to-use/when-not statement, no mention of alternatives such as buy_fx_ils or buy_pm_israel for related-but-different data, and no guidance on staleness or repeat calls.

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