Skip to main content
Glama

SouthPow crypto & market data

buy_econ_nl

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and it does a decent job: it discloses cost ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — meaningful billing behavior. It says nothing about response format, data vintage/refresh cadence beyond 'latest', or what happens if payment succeeds but the upstream fetch fails.

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 and front-loaded: payment status first, then the payload, then commercial terms. The wage is telegraphic sentence fragments and the trailing raw URL adds little an agent can act on, but otherwise every clause carries information.

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-output-schema tool, the description covers the important gaps: what data is returned, its source, its recency, the price, the payment rails, and the auth requirement. What is missing is the shape of the returned payload (field names, units, JSON structure) and staleness/caching semantics, which is a moderate omission rather than a blocking one.

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 meaning to add; the baseline of 4 applies. The description usefully fixes the one dimension that would otherwise be a variable (country = NL) and states the data source, so nothing is left ambiguous about the call.

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 (economic data for country NL) and enumerates exactly which indicators come back — GDP, GDP growth, inflation, unemployment, population, GDP per capita — plus the upstream source (latest World Bank values). That is enough to tell it apart from the large buy_econ_* family by country code, though the distinguishing scope is conveyed by the 'NL' token rather than an explicit statement.

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 rather than stated: the 'Paid' prefix and price line signal this is a paid data purchase, and the country token implies it is the NL member of a country series. There is no explicit when-to-use vs. alternatives (e.g. buy_econ_de, buy_econ_us) and no statement of when not to call it, so the agent must infer routing from the name.

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