Skip to main content
Glama

SouthPow crypto & market data

buy_econ_no

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

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

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 calls are paid ($0.002 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that values come from the latest World Bank data. It stops short of describing the response shape or what happens on partial failures.

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?

Front-loads 'Paid.' so cost is known before anything else, then the resource, the data fields, the price/rail, the auth posture, and the billing-failure policy in tight sequence. Every sentence carries distinct information and nothing is repeated from structured fields.

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 essentials: what data, from what source, at what cost, on which chains, and failure billing. Only the response structure/data units (e.g. currency, year basis) are unstated, which is a modest gap given no output schema exists.

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 schema has zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The field list effectively documents what the response will contain, which is a useful surrogate for parameter semantics here.

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 resource (economic data for country NO) and enumerates the exact metrics returned: GDP, GDP growth, inflation, unemployment, population, GDP per capita. That distinguishes it from the many buy_econ_* siblings, though it never expands 'NO' to Norway, leaving a small ambiguity for an agent scanning country codes.

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 — this is the Norway variant of the buy_econ_* family, so select it when Norwegian macro data is wanted. There is no explicit when-to-use/when-not guidance, no mention of complementary or overlapping tools (e.g. buy_fx_ or buy_pm_ tools) an agent might confuse it with, and no note on data recency choices.

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