Agent Tools

macro_indicators

Macro indicators by country and year from the World Bank: GDP, GDP growth, GDP per capita, inflation, unemployment, population, debt to GDP, real interest rate, exports, imports, current account, FDI, or any World Bank indicator code. Up to 10 countries per call (ISO2 or ISO3, joined with ;), newest year first. Pairs with fx_rates. Price $0.003 USDC per call via x402. Example output: {"indicator":{"code":"NY.GDP.MKTP.CD","name":"GDP (current US$)"},"series":[{"country":"United States","iso3":"USA","values":[{"year":2025,"value":30769700000000},{"year":2024,"value":29298013000000}]}],"last_updated":"2026-10-08","source":"World Bank Open Data API (CC BY 4.0)"}

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
`to`	No	Optional last year
`from`	No	Optional first year
`limit`	No	1 to 60 values per country, default 10
`country`	No	ISO2 or ISO3 code, or up to 10 joined with ;, default US
`indicator`	No	Alias such as gdp or inflation, or a World Bank code like NY.GDP.MKTP.CD

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the whole burden and does well: it discloses the paid x402 model ($0.003 USDC per call), the upstream source and license, default country (US) and default limit (10), and result ordering. It omits error/failure behavior and whether billing applies to failed calls.

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-loads what the tool returns and its scope, then constraints, then pricing and an example. The inline output sample is long but earns its place since there is no output schema. Slight density cost from packing an entire indicator list mid-sentence.

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 5-param tool with no output schema and no annotations, the description supplies the missing return shape via a worked example, plus pricing and source attribution. Only edge behavior (empty results, invalid indicator codes, interaction of limit with from/to) is left unstated.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by listing accepted indicator aliases (gdp, inflation, debt to GDP...) and the ISO2/ISO3 plus ';' multi-value convention, which the schema only states tersely.

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?

Names a specific resource (World Bank macro indicators), the dimensions (country, year), and enumerates the indicator vocabulary including a catch-all 'any World Bank indicator code'. An agent can distinguish this from fx_rates or sec_facts without opening the schema.

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 concrete operating constraints — up to 10 countries per call, ISO2/ISO3 joined with ';', newest year first — and points to a companion tool ('Pairs with fx_rates'). It does not state when to prefer it over a full web_read_full or another data source, so no explicit exclusions.

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

All Agent Tools 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?