Skip to main content
Glama

SouthPow crypto & market data

buy_econ_tr

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 well: it discloses that the call is paid ($0.005 USDC), the accepted payment chains (Base or Solana), no account or API key requirement, and that failed calls are not charged — all non-obvious operational facts. It stops short of describing the response payload shape, update cadence, or latency, which matters since there is no output schema.

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-loaded with 'Paid.' followed by scope, indicators, price, and access terms — every sentence carries information. The trailing raw URL is mildly redundant with the tool name but serves as a transparency signal for a paid endpoint, so it earns most of its place.

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, no-annotation, no-output-schema tool, this covers the essentials an agent needs before spending money: what data, which country, which source, what cost, and that failures are free. The only meaningful gap is the absence of any indication of response structure or data vintage beyond 'latest'.

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, which is the baseline-4 case. The description appropriately adds no parameter detail and instead spends its words on cost and data source, which is the right allocation for a parameterless endpoint.

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?

The description names the resource precisely — economic data for country TR — and enumerates the specific indicators returned (GDP, GDP growth, inflation, unemployment, population, GDP per capita) plus the source (latest World Bank values). It distinguishes itself from the large buy_econ_XX sibling family mainly through the 'TR' country code rather than an explicit statement, so it is clear but not maximally differentiated.

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: an agent can infer this is the Turkey macro-indicator endpoint within a per-country family. However, it gives no explicit when-to-use guidance relative to adjacent siblings such as buy_fx_try (currency rates) or buy_pm_inflation (prediction markets), and no statement about freshness or whether other countries' tools share identical semantics.

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