worldbank-mcp-server

List World Bank Data Sources

worldbank_list_sources

Read-onlyIdempotent

List the 70+ World Bank data sources (datasets), such as World Development Indicators, International Debt Statistics, and Doing Business. Returns source IDs and names for use as source_id in worldbank_search_indicators, one page at a time.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Pagination page number (1-based).
`per_page`	No	Results per page (default: server default, max: 100).

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Context for an empty page: the page range that exists when the requested page is past the end.
`sources`	No	World Bank data sources for this page.
`totalCount`	No	Total number of sources.
`totalPages`	No	Total number of pages.
`currentPage`	No	Page number requested — past totalPages when the request ran off the end.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 12, 2026

changedOutput schema / properties / currentPage / description

Previous value: -"Current page number."New value: +"Page number requested — past totalPages when the request ran off the end."

addedOutput schema / properties / notice

Added value: +{
+  "description": "Context for an empty page: the page range that exists when the requested page is past the end.",
+  "type": "string"
+}

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "sources",
+      "totalCount",
+      "currentPage",
+      "totalPages"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode.",
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "sources",
-  "totalCount",
-  "currentPage",
-  "totalPages"
-]

Changed7 schema fields changedMay 30, 2026

addedOutput schema / properties / currentPage

Added value: +{
+  "description": "Current page number.",
+  "type": "number"
+}

removedOutput schema / properties / page

Removed value: -{
-  "description": "Current page number.",
-  "type": "number"
-}

removedOutput schema / properties / pages

Removed value: -{
-  "description": "Total number of pages.",
-  "type": "number"
-}

removedOutput schema / properties / total

Removed value: -{
-  "description": "Total number of sources.",
-  "type": "number"
-}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total number of sources.",
+  "type": "number"
+}

addedOutput schema / properties / totalPages

Added value: +{
+  "description": "Total number of pages.",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "sources",
-  "total",
-  "page",
-  "pages"
-]New value: +[
+  "sources",
+  "totalCount",
+  "currentPage",
+  "totalPages"
+]

First observedMay 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the result set is bounded at 70+ sources and retrieval is paginated ('one page at a time'), which tells the agent to expect multiple calls.

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?

Two sentences, front-loaded with what is listed and followed by the downstream purpose. Every clause carries information; nothing is redundant.

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?

Covers scope (70+ sources), examples, downstream usage of the returned IDs, and pagination behavior, and an output schema exists so return values need no further explanation. An agent has everything needed to call it correctly.

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 page and per_page are already fully documented in the schema. The description only alludes to pagination generically ('one page at a time') and adds no format or constraint detail beyond the schema, so 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 ('List the 70+ World Bank data sources (datasets)') and grounds it with concrete examples (WDI, IDS, Doing Business). It also distinguishes itself from siblings by naming worldbank_search_indicators as the consumer of the returned source IDs.

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 context: use this to obtain source IDs that feed worldbank_search_indicators, and it operates one page at a time. It does not state when NOT to use it (e.g., versus worldbank_list_topics or list_countries), so it stops short of full exclusion guidance.

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

All worldbank-mcp-server 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.