Skip to main content
Glama

SouthPow crypto & market data

buy_econ_vn

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 load and does well: it discloses that the call is paid ($0.002 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. The remaining gap is the response shape/pagination, which is never described and there is no output schema to fall back on.

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?

Front-loads the critical 'Paid.' signal, then scope, then payment mechanics, then endpoint. The telegraphic sentence fragments are efficient; the raw URL is the only element that could arguably be structured metadata rather than prose.

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-param, fixed-endpoint data tool, the definition covers what is needed to decide and pay: indicators, source freshness, price, chains, and failure policy. The one material omission is what the returned payload looks like, which matters more here because no output schema exists.

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 schema declares zero parameters, so the baseline of 4 applies. The description correctly implies a fully parameterless call — the country is baked into the endpoint URL it publishes.

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 VN) and enumerates the exact indicators returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. Combined with the VN suffix, an agent can distinguish it from the roughly 50 other buy_econ_* siblings without opening any 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?

Usage is implied by 'country VN' and '(latest World Bank values)', but the description never states when to prefer this over a sibling like buy_econ_us or a non-paid data source, nor any exclusion. An agent must infer the routing rule from the country code alone.

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