worlduank

Get Indicator

get_indicator

Read-onlyIdempotent

Get World Bank time-series data — economic, social, and development statistics — for ANY country worldwide (Spain, Brazil, Germany, Nigeria, Japan, etc.). PREFER for "unemployment rate in ", " inflation rate", "GDP of ", " population / life expectancy / poverty rate / CO2 emissions". Pass the ISO country code + a World Bank indicator code; common ones: GDP=NY.GDP.MKTP.CD, GDP per capita=NY.GDP.PCAP.CD, inflation=FP.CPI.TOTL.ZG, unemployment=SL.UEM.TOTL.ZS, population=SP.POP.TOTL, life expectancy=SP.DYN.LE00.IN, poverty rate=SI.POV.DDAY, literacy=SE.ADT.LITR.ZS. For CO2 use the dedicated country_co2_emissions tool (the old EN.ATM.CO2E.* codes were DELETED by the World Bank; the live series is EN.GHG.CO2.MT.CE.AR5). (Annual data — a national statistics office may have fresher monthly figures.)

Input Schema

TableJSON Schema

Name	Required	Description
`indicator`	Yes	World Bank indicator code (e.g., "NY.GDP.MKTP.CD", "SP.POP.TOTL")
`date_range`	No	Year range in format "start:end" (default: 2015:2024). Example: "2000:2023"
`country_code`	Yes	ISO country code (e.g., "US", "GBR", "CN")

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Time-series data points sorted by year descending
`country`	Yes	Country name or code
`country_id`	Yes	World Bank country ID
`date_range`	Yes	Requested date range in start:end format
`indicator_id`	Yes	World Bank indicator code
`last_updated`	Yes	Last update timestamp from World Bank API
`total_records`	Yes	Total number of records available
`indicator_name`	Yes	Full indicator name/description

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "description": "Country name or code",
+      "type": "string"
+    },
+    "country_id": {
+      "description": "World Bank country ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "data": {
+      "description": "Time-series data points sorted by year descending",
+      "items": {
+        "properties": {
+          "value": {
+            "description": "Indicator value for the year",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Year of the observation",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "date_range": {
+      "description": "Requested date range in start:end format",
+      "type": "string"
+    },
+    "indicator_id": {
+      "description": "World Bank indicator code",
+      "type": "string"
+    },
+    "indicator_name": {
+      "description": "Full indicator name/description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_updated": {
+      "description": "Last update timestamp from World Bank API",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_records": {
+      "description": "Total number of records available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "country",
+    "country_id",
+    "indicator_id",
+    "indicator_name",
+    "date_range",
+    "total_records",
+    "last_updated",
+    "data"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "country_code": "CN",
+    "indicator": "NY.GDP.MKTP.CD"
+  },
+  {
+    "country_code": "IN",
+    "date_range": "2000:2023",
+    "indicator": "SP.POP.TOTL"
+  }
+]

First observedApr 14, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond annotations (readOnly, openWorld, idempotent), the description discloses behavioral traits: data is annual, old CO2 codes were DELETED by the World Bank, and a live series is provided. This adds valuable context about data freshness and source changes, complementing the annotation coverage.

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?

The description is long but every sentence earns its place: purpose, usage examples, parameter guidance, CO2 warning, and data freshness are all included. It is front-loaded with the main definition and organized logically, with no wasted words.

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 the tool's complexity and the availability of an output schema, the description is highly complete. It covers purpose, when to use, parameter selection, known caveats, and data limitations. The mention of annual data granularity and the CO2 exception ensures agents have the full context needed to invoke the tool 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%, but the description adds significant meaning by listing common indicator codes and their meanings (e.g., GDP=NY.GDP.MKTP.CD, inflation=FP.CPI.TOTL.ZG). This goes beyond the schema's generic 'World Bank indicator code' and helps agents select the correct code.

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 the tool's function: 'Get World Bank time-series data — economic, social, and development statistics — for ANY country worldwide.' It uses a specific verb ('Get') and resource ('World Bank time-series data'), and differentiates from siblings by explicitly naming the country_co2_emissions tool for CO2 and listing example queries.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'PREFER for "unemployment rate in <country>"...' and for CO2 'use the dedicated country_co2_emissions tool.' It also notes that annual data may be less fresh than national statistics office figures, giving clear context for alternative sources.

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

All worlduank 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.