Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@World Bank MCP Server show me the population growth rate for India over the last 5 years"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that enables interaction with the open World Bank data API. This server allows AI assistants to list indicators and analyse those indicators for the countries that are available with the World Bank.
List available countries in the World Bank open data API
List available indicators in the World Bank open data API
Analyse indicators, such as population segments, poverty numbers etc, for countries
Comprehensive logging
Related MCP server: world-bank-server
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"world_bank": {
"command": "uv",
"args": [
"--directory",
"path/to/world_bank_mcp_server",
"run",
"world_bank_mcp_server"
]
}
}
}To install World Bank Data Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @anshumax/world_bank_mcp_server --client claudeGet values for an indicator for a specific country from the World Bank API
| Name | Required | Description | Default |
|---|---|---|---|
| country_id | Yes | The ID of the country for which the indicator is to be queried | |
| indicator_id | Yes | The ID of the indicator to be queried |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the data source (World Bank API), it doesn't describe what kind of values are returned, potential rate limits, authentication requirements, error conditions, or whether this is a read-only operation. For a tool with no annotation coverage, this leaves significant behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a simple tool with two parameters. However, it could be slightly more front-loaded with key behavioral information given the lack of annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read operation with 2 parameters and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, the description should ideally provide more context about what kind of data is returned and any behavioral considerations. The World Bank API mention is helpful but insufficient for full completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with both parameters clearly documented in the input schema. The description doesn't add any additional parameter information beyond what's already in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get values') and target resource ('indicator for a specific country from the World Bank API'), making the purpose immediately understandable. It specifies the data source (World Bank API) which adds useful context. However, since there are no sibling tools mentioned, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives or any contextual prerequisites. It simply states what the tool does without mentioning when it's appropriate or any limitations. With no sibling tools, the bar is lower, but it still lacks any usage context beyond the basic function.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
get_indicator_for_countryWith 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).
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Access World Bank development indicators for 200+ countries.
Query 29,500+ World Bank development indicators for 200+ countries across 60+ years.
Dive into the wealth of information provided by the World Bank with our zero-auth API. Instantly
World Bank World Development Indicators: curated country-year economy, health, education and more.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/anshumax/world_bank_mcp_server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server