Skip to main content
Glama

SouthPow crypto & market data

buy_econ_ae

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses cost, accepted payment chains, the absence of auth prerequisites, and the failure-pricing policy ('Failed calls not charged'). It also flags data provenance and vintage ('latest World Bank values'), warning the agent that figures are not real-time. It does not describe response shape or rate limits, which keeps it from 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?

Three compact sentences, leading with 'Paid' so cost is known before commitment, then data scope, then payment and endpoint details. No sentence is redundant; even the URL earns its place as an endpoint reference.

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

Completeness5/5

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

For a zero-parameter tool with no output schema, the description supplies everything needed: what data comes back, how fresh it is, what it costs, how to pay, and that failures are free. Nothing an agent needs in order to decide and invoke correctly is missing.

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 of 4 applies; there is no parameter meaning the description needs to supply. The listed indicator names act as a lightweight substitute for output documentation without overclaiming.

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?

States a specific resource (economic data for country AE) and enumerates exactly which indicators are returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The country-code suffix plus the sibling naming pattern (buy_econ_us, buy_econ_gb, etc.) makes the scope unambiguous without opening the schema.

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?

Operational conditions are clear (paid, $0.005 USDC on Base or Solana, no account or API key, failures not charged), which tells the agent how to invoke it. However, it never explicitly states when to choose this over a sibling such as buy_econ_us or buy_econ_sa, leaving the country-routing inference implicit in the tool name.

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