Skip to main content
Glama

SouthPow crypto & market data

buy_econ_fi

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

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

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 that the call is paid, the exact price ($0.005 USDC), the accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing the response shape or data freshness/refresh cadence beyond 'latest World Bank values'.

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?

Front-loads 'Paid' so the agent knows the cost model immediately, then the data scope, then the price, payment rails, and failure policy. Every clause carries distinct information; nothing is repeated from the empty schema.

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-param, no-output-schema tool the description supplies what an agent needs to decide and pay: data covered, source, price, chains, auth, and failure billing. The only gap is what the response payload looks like (format, units, time coverage), which no output schema supplies either.

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 semantic burden is nil and the baseline is 4. The description correctly offers no parameter guidance and instead spends its words on cost and data source, which is the right allocation.

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 (macroeconomic indicators for Finland) and enumerates the exact fields returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The country code FI plus the field list makes it unmistakable against the many buy_econ_* siblings, each differing only by country suffix.

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 implied by the country-scoped field list and the 'Paid' opener, but there is no explicit when-to-use or when-not guidance and no named alternative (e.g., buy_econ_se, buy_econ_us, or search_facts). An agent must infer selection from the FI suffix alone.

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