Skip to main content
Glama

world-bank-data

Retrieve World Bank development indicators for any country: GDP, population, inflation, unemployment, and more. Get most-recent values and 5-year trends using short aliases or official codes.

Instructions

World Bank open data — 1600+ development indicators for 200+ countries. Returns most-recent values and 5-year trend for any indicator by country. Covers GDP, population, inflation, unemployment, FDI, debt, exports, CO₂, life expectancy, Gini, internet penetration, ease of doing business, and more. Accepts ticker-style aliases (gdp, inflation, unemployment) or full WB indicator codes. Sourced from api.worldbank.org — free, no key required. Use for country risk, macro comparisons, policy analysis, and development economics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoISO 2-letter country code(s), semicolon-separated for multiple (e.g. 'US', 'US;CN;DE'). Use 'WLD' for world average.
indicatorNoIndicator alias or WB code. Aliases: gdp, gdp_growth, gdp_per_capita, population, inflation, unemployment, fdi, debt_gdp, exports_gdp, imports_gdp, co2_per_capita, internet_users, life_expectancy, gini, literacy, ease_of_biz, current_account, market_cap_gdp, forex_reserves. Or any WB indicator code like 'NY.GDP.MKTP.CD'.
yearsNoNumber of most-recent years to return (1–10). Default: 5.
Behavior4/5

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

No annotations provided, so description carries the burden. It discloses data source, free usage, no key required, and returns most-recent values with 5-year trend. Lacks details on rate limits but sufficient for a read-only API.

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?

Description is comprehensive but not overly verbose; each sentence adds information. Minor redundancy (e.g., listing indicators both in text and schema) but generally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters and no output schema, the description fully covers input expectations, return behavior, and use cases. No missing critical information for an agent to invoke correctly.

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

Parameters5/5

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

Schema coverage is 100%. The description adds significant value by explaining alias system, default years, semicolon-separated countries, and the 'WLD' code for world average, going beyond schema descriptions.

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 clearly states it returns World Bank open data with 1600+ development indicators for 200+ countries, listing specific indicators and aliases. It distinguishes from many sibling tools by its focus on development economics.

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?

The description mentions use cases (country risk, macro comparisons, policy analysis, development economics) but does not explicitly state when not to use or provide alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thebrierfox/the-stall'

If you have feedback or need assistance with the MCP directory API, please join our Discord server