Skip to main content
Glama

SouthPow crypto & market data

buy_econ_ar

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 disclose several important traits: paid ($0.005 USDC), payment rails (Base or Solana), no account/API key required, and that failed calls are not charged. It does not describe the response shape, payment flow, latency, or whether the call is a plain read, leaving meaningful gaps for a paid tool.

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?

Short and front-loaded with the paid nature and the payload, followed by price, payment options, billing policy, and endpoint. The telegraphic fragments ('Paid.', bare URL) are slightly rough but every sentence carries information an agent needs.

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, fixed-country paid endpoint with no output schema, the description covers what data, what source, what cost, how to pay, and failure billing. The main omission is the return format, which is not covered by any output schema.

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 is 4. The description instead usefully pins down what the fixed call returns (a specified metric set for a fixed country), which is more than the empty schema conveys.

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 and scope: economic data for country AR, then enumerates the exact metrics returned (GDP, growth, inflation, unemployment, population, GDP per capita) and the source (latest World Bank values). Combined with the country-suffixed name, an agent can distinguish this from the ~50 sibling buy_econ_* tools without opening anything else.

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 infers it should call this for Argentina macro data. There is no explicit when-to-use/when-not statement, no mention of what to do if a different country is needed (the sibling set), and no guidance on freshness beyond 'latest World Bank values'.

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