Skip to main content
Glama

SouthPow crypto & market data

buy_econ_eg

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

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

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 disclosure burden and does well: exact price, accepted payment chains (Base or Solana), absence of auth requirements, the fact that failures are not billed, and the underlying endpoint plus data provenance. It stops short of rate limits, whether results are cached or refreshed, and how payment is actually settled by the client, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short, front-loaded fragments: price signal, data payload, payment/auth terms, endpoint. Every clause carries operational information (cost, chain, auth, billing on failure), with no filler. The trailing bare URL is slightly machine-flavored but adds the real endpoint, so it earns its space.

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 endpoint, the description covers what an agent must know before spending money: cost, currency, chains, no credentials required, failure billing, and the exact fields returned. The only real gap is the response shape/format, which is not strictly required absent an output schema but would help the agent plan parsing.

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 and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the country is baked into the tool identity rather than being a parameter, so no per-call semantics 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?

The description names the resource precisely ('Economic data for country EG') and enumerates the returned indicators (GDP, GDP growth, inflation, unemployment, population, GDP per capita) plus their source (latest World Bank values). That is enough to separate it from buy_econ_us/buy_econ_fr and the buy_coin_* siblings. It loses a point only because the action verb is implicit – the text opens with 'Paid.' rather than stating that the call fetches the data.

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?

'Paid' plus the '$0.005 USDC on Base or Solana' and 'No account, no API key' lines tell the agent what it must accept before calling, and 'Failed calls not charged' sets the risk profile. However, there is no explicit routing guidance – nothing says when to pick this over the country lookups in other services (buy_fx_*, buy_pm_inflation) or that buying multiple country codes is the intended pattern for cross-country queries.

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