Skip to main content
Glama

SouthPow crypto & market data

buy_econ_be

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does well on the commercial/operational side: price of $0.01 USDC, accepted chains (Base or Solana), no account or API key required, and failed calls are not charged. It says nothing about the response shape, units, currency of GDP figures, or whether values are cached, so an agent still can't predict what comes back.

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?

Five short, front-loaded fragments: payment status first, then content, then price/chains, then auth, then the endpoint URL. Every sentence carries a distinct fact and nothing is repeated.

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 parameterless, single-purpose data endpoint with no output schema, the definition covers the essentials an agent needs to decide and transact: what data, what it costs, how to pay, and that failures are free. The only material gap is the absence of any hint about the returned structure or the vintage of the 'latest World Bank values'.

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 no parameter meaning to add; the baseline applies. The description usefully confirms that country selection is baked into the tool rather than passed in, which prevents an agent from searching for a country argument.

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?

The description names a specific verb (a paid purchase/retrieval), a specific resource (economic data for country BE) and enumerates the metrics returned (GDP, growth, inflation, unemployment, population, GDP per capita). That distinguishes it cleanly from the many buy_econ_XX siblings and from unrelated tools like buy_crypto_price.

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 Belgian macro data from World Bank values. There is no explicit statement of when not to use it, no pointer to alternative sources (e.g. FX or prediction-market siblings), and no note about how fresh or how often-refreshed the data is.

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