Skip to main content
Glama

SouthPow crypto & market data

buy_econ_ng

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

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

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 supplied, the description carries the full behavioral burden and does a solid job: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, and critically that failed calls are not charged — a material risk fact for a paid tool. It stops short of describing how payment is presented (e.g., 402 flow), whether the payment is per call or per session, or any rate limits, and there is no output schema to cover the response shape.

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?

Four short sentences with no filler; 'Paid.' is front-loaded so the cost signal hits before the agent commits. The ordering (cost terms before the data description in the second half) is slightly inverted, and the bare URL at the end could be labelled, but nothing is wasted.

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 paid fetch tool, the definition covers what an agent needs: the dataset contents (functioning as an implicit return-value list), the data source and vintage, the price, accepted chains, and that failures are free. The remaining gaps — response format, units, and whether figures are nominal or real — are modest but real given there is no output schema to fall back on.

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 empty schema is fully self-explanatory. Baseline of 4 applies. The description correctly implies the country is baked into the endpoint rather than selectable, which prevents an agent from guessing at a country argument.

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 NG) and enumerates the exact series returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. That makes it separable from the 48 other buy_econ_* siblings only implicitly, via the country code in the name and the phrase 'country NG'; there is no explicit statement that other countries use other tools. It also lacks an explicit verb ('get'/'return'), though the intent is unmistakable.

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 rather than stated: an agent infers 'call this when you need Nigerian macro data'. The description adds decision-relevant context — 'latest World Bank values' tells the agent the freshness/vintage — but never says when not to use it or names an alternative (e.g., other country tools, buy_fx, buy_pm_inflation). No prerequisites or exclusions are given.

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