Skip to main content
Glama

SouthPow crypto & market data

buy_econ_dk

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

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

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 behavioral burden and does well: it discloses that this is a paid call ($0.005 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. What it omits is the payment mechanics (how the USDC is collected, e.g. an x402-style challenge) and whether the returned World Bank figures are cached or refreshed on each call.

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?

It is short, front-loaded with the paid status and the resource, and every fragment carries information (metrics, source, price, auth model, billing guarantee, endpoint URL). The telegraphic style costs a little readability, but there is no redundant sentence to cut.

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?

With no parameters, no annotations and no output schema, the description must supply everything, and it covers cost, auth model, billing behaviour, data source and content. The remaining gap is the response shape and payment flow, which an agent may need in order to actually complete a paid call correctly.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description compensates usefully by listing the data fields that the fixed call yields, which is the closest analogue to parameter information here.

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?

The description names a specific resource (economic data for country DK) and enumerates exactly which metrics are returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. It also states the upstream source (latest World Bank values), so an agent knows precisely what it is buying and can distinguish it from the many buy_econ_* siblings by country code.

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 context is implied rather than stated: the country-code suffix and the enumerated metrics make the when-to-use case evident, and it notes there is no account or API key needed. However, it never explicitly says when to prefer this over near alternatives such as buy_fx_dkk or buy_econ_us, nor does it warn about cases where the call is unnecessary.

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