Skip to main content
Glama

SouthPow crypto & market data

buy_econ_sg

Paid. Economic data for country SG: GDP, GDP growth, inflation, unemployment, population, GDP per capita (latest World Bank values). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/economic/sg.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 well: it discloses that the call is paid, the exact price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits how the payment is settled and what the response payload looks like after payment.

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 tight, front-loaded sentences: what you get, what it costs and how you pay, then the endpoint. Every clause earns its place, and the paid/access constraints come before the raw URL.

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 parameterless paid data endpoint with no output schema, the description covers cost, payment rails, access requirements, billing failure policy, data provenance and indicator scope. The remaining gap is the shape of the returned data and how a 402/payment challenge manifests, which an agent must discover at call time.

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; there is nothing for the description to disambiguate. It usefully confirms the country is fixed by the endpoint URL, so an agent knows no country argument is expected.

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?

States the resource precisely: economic data for country SG, enumerating the exact indicators returned (GDP, growth, inflation, unemployment, population, GDP per capita) and the source (World Bank). The country code in the text implicitly separates it from the ~50 sibling buy_econ_XX tools, though no sibling is named explicitly.

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 country code and indicator list — an agent can infer this is the Singapore macro-data purchase — but the description never states when to choose it over alternatives (e.g., buy_econ_us or buy_fx_sgd) or any precondition such as needing a funded wallet on Base or Solana.

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