Skip to main content
Glama

SouthPow crypto & market data

buy_econ_se

Paid. Economic data for country SE: GDP, GDP growth, inflation, unemployment, population, GDP per capita (latest World Bank values). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/economic/se.

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

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 at all, the description carries the full burden and does well: it discloses that the call is paid ($0.002 USDC), the accepted payment rails (Base or Solana), that no account or API key is required, that failed calls are not charged, and that values are the latest World Bank figures. It omits the response format, latency, and what happens on partial payment failure, which keeps it short of a 5.

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-loaded with the single most decision-relevant fact ('Paid.'), then scope, then price and payment mechanics, then the endpoint. Every clause carries distinct information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There are no annotations and no output schema, so the description must also convey what comes back; it lists the covered indicators, which partially compensates, but never describes the response shape, units, currency basis, or the reference year of the 'latest' values. For a zero-param paid data fetch that is adequate but leaves a real gap.

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 the baseline is 4. The description correctly implies a parameterless call by fixing the country and indicator set internally, and clarifies that no credential parameters are needed.

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?

States a specific verb and resource: economic data for country SE, enumerating the exact indicators returned (GDP, GDP growth, inflation, unemployment, population, GDP per capita) and the source (World Bank). The country code 'SE' is never expanded to Sweden, so an agent must infer the sibling family mapping, but the resource scope is otherwise unambiguous.

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 sibling naming convention: pick buy_econ_XX for the country you want. The description adds useful preconditions (paid, no account, no API key), but never states when NOT to use it or what alternative exists if the caller needs historical series, non-latest figures, or a different country.

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