Skip to main content
Glama

SouthPow crypto & market data

buy_econ_my

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

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

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 supplied, the description carries the full burden and does it well: it discloses the paid nature, the exact price ($0.01 USDC), the two accepted chains (Base or Solana), that no account/API key is required, and that failed calls are not charged. This is precisely the behavioral context an agent needs before a paid call. It is only slightly short of 5 because it doesn't describe the response shape or units/currency of the values.

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?

A single dense paragraph that front-loads the most decision-relevant fact ('Paid') and packs price, auth, failure policy, and data contents without filler. The trailing bare URL is slightly unpackaged but not wasteful.

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, no-output-schema lookup tool, the description supplies everything needed to call it correctly: what data comes back, its source and recency (latest World Bank values), the cost, the payment rails, and the failure billing policy. Nothing material 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 is 4 and no parameter-level clarification is needed or expected. The description correctly implies the country is fixed by the endpoint rather than passed as an argument.

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 a specific verb+resource (economic data for country MY) and enumerates the exact metrics returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. The country-code suffix distinguishes it from the dozens of buy_econ_* siblings, though it never expands 'MY' to Malaysia, so the agent must know ISO codes to route correctly.

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?

The description implies the usage context (fetching Malaysia macro data) and covers prerequisites well ('No account, no API key'), but it gives no explicit when-to-use guidance, no exclusions, and never mentions that other countries are served by separate siblings such as buy_econ_sg or buy_econ_us. Usage is inferable rather than stated.

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