Skip to main content
Glama

SouthPow crypto & market data

buy_econ_bd

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

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

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 behavioral burden and does well: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is needed, that failed calls are not charged, and that values come from the World Bank. It stops short of stating the response format or how stale 'latest' values can be, which matters for a paid call.

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?

Compact and well ordered: cost/payment status first, then the data covered, then access requirements, then the endpoint. Each sentence carries distinct information, though the price sentence packs three facts into one fragment and the URL is of marginal value to an agent that cannot fetch it.

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 tool, the description covers what is returned, the data source and recency, the cost, and the auth requirements — enough for an agent to decide and invoke. The remaining gap is data shape (single snapshot vs. series) and freshness, which nothing else in the definition supplies.

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 input schema has zero parameters, so there is no parameter meaning to add; the baseline for a 0-param tool is 4. The description correctly makes clear that country and metrics are fixed, not 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 BD) and enumerates the exact payload: GDP, GDP growth, inflation, unemployment, population, GDP per capita. That distinguishes it from the many buy_econ_XX country siblings only implicitly via the 'BD' code; it never says 'Bangladesh' or routes to other country tools, so the sibling differentiation is carried by the tool name rather than the prose.

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 payload list, and the purchase mechanics ('Paid', '$0.002 USDC on Base or Solana', 'No account, no API key') tell the agent what is required to call it. However, there is no explicit when-to-use guidance — nothing says to use buy_econ_us for US figures, to prefer this over buy_fx for currency rates, or what to do if payment is unavailable.

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