Country Macro Indicators (World Bank)

macro_indicators

Get official macro figures for a country for research, market sizing or country-risk work. Returns World Bank World Development Indicators for up to 5 of ~217 economies: GDP, GDP per capita, real growth, CPI inflation, unemployment, population, government debt, trade, FDI or any WDI code, latest years with the year of each value. Use when a figure must be citable to an official source. $0.005 per call, USDC on Base (x402).

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": "macro_indicators"
  }
}

Input Schema

Name	Required	Description
`years`	No	Most recent years per indicator, 1-10 (default 3)
`countries`	No	Comma list of ISO2/ISO3 codes, up to 5 (e.g. DE,DK,USA)
`indicators`	No	Comma list of short names (gdp, gdp_per_capita, gdp_growth, inflation, unemployment, population, debt, current_account, exports, fdi, interest_rate) or WDI codes; default core set
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations, so the description carries the full burden and does well: it discloses the data source (World Bank WDI), the coverage cap (5 economies), that each value carries its year, and an explicit pricing/settlement model ($0.005 per call, USDC on Base/x402). It does not describe error modes or what the response body structure looks like, but the behavioral profile is otherwise rich.

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?

Three sentences, front-loaded with purpose and scope, then the data source, then the citation qualifier and pricing. Every sentence carries distinct information with no padding.

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 4-param read tool with no output schema and no annotations, the description covers purpose, source, scope, citation use-case and monetization. It omits any mention of return shape or failure/payment-required behavior, which for a paid x402 tool would be useful, but the schema's payment_signature note partially covers that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters including the payment_signature handshake. The description restates the economy cap and indicator vocabulary but adds no syntax or format detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ('Get official macro figures for a country') and enumerates the exact indicator set (GDP, inflation, unemployment, etc.) plus the source (World Bank WDI). No siblings exist to differentiate from, and the scope (up to 5 of ~217 economies) is concrete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use framing ('research, market sizing or country-risk work' and 'when a figure must be citable to an official source'). No explicit when-not-to-use or excluded cases are provided, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Country Macro Indicators (World Bank) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?