World Bank MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_indicator_for_countryC | Get values for an indicator for a specific country from the World Bank API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Countries list | List of countries in the World Bank database |
| Indicators list | List of indicators in the World Bank database |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get_indicator_for_country' follows a clear verb_noun pattern.
A single tool is too few for a server named 'World Bank MCP Server', which implies access to a broad dataset (e.g., indicators, countries, years). This minimal surface will likely cause agent failures due to lack of flexibility (e.g., no search, filtering, or multi-country queries).
The tool set is severely incomplete for the domain. It only allows fetching a single indicator for a single country, missing essential operations like listing indicators, getting data for multiple countries or years, searching metadata, or accessing other World Bank datasets (e.g., projects, finances).