Skip to main content
Glama

Worldbank Get Indicator

worldbank_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", "what share of GDP comes from agriculture in " / "agriculture's share of GDP". 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, agriculture value added (% of GDP)=NV.AGR.TOTL.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). For governance/corruption/rule-of-law/political-stability use the dedicated get_governance_indicators tool (Worldwide Governance Indicators, codes like GOV_WGI_CC.EST). Several countries over time in one call ("cereal yield in Brazil, Argentina and the US over the past decade", "inflation in Spain vs Italy since 2015"): pass up to 8 codes separated by ";", each country comes back as its own series. Agriculture: cereal yield (kg per hectare)=AG.YLD.CREL.KG. (Annual data, a national statistics office may have fresher monthly figures.)

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "indicator": "NY.GDP.MKTP.CD",
      "country_code": "CN"
    },
    "name": "worldbank_get_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
indicatorYesWorld Bank indicator code (e.g., "NY.GDP.MKTP.CD", "SP.POP.TOTL")
date_rangeNoYear range in format "start:end" (default: 2015:2024). Example: "2000:2023"
country_codeYesISO country code (e.g., "US", "GBR", "CN"). For a multi-country comparison over time pass up to 8 codes separated by ";" (e.g., "US;BR;AR"), one series per country.

Output Schema

NameRequiredDescriptionDefault
dataYesTime-series data points sorted by year descending
countryYesCountry name or code
country_idYesWorld Bank country ID
date_rangeYesRequested date range in start:end format
indicator_idYesWorld Bank indicator code
last_updatedYesLast update timestamp from World Bank API
total_recordsYesTotal number of records available
indicator_nameYesFull indicator name/description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country_code / description
      Previous value: -"ISO country code (e.g., \"US\", \"GBR\", \"CN\"). For a multi-country comparison over time pass up to 8 codes separated by \";\" (e.g., \"US;BR;AR\") — one series per country."New value: +"ISO country code (e.g., \"US\", \"GBR\", \"CN\"). For a multi-country comparison over time pass up to 8 codes separated by \";\" (e.g., \"US;BR;AR\"), one series per country."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: data is annual, national statistics offices may have fresher monthly figures, and multi-country calls return one series per country. It does not cover rate limits or response shape, but the output schema handles the latter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information is front-loaded and nearly every clause carries routing value, but the prose is a run-on with long parenthetical asides, and the trailing agriculture/cereal-yield sentence is tacked on awkwardly after the main block. A bulleted code table would deliver the same content with less parsing effort.

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?

An output schema exists, so return values need not be described. Given three parameters with full schema coverage, the description covers what remains: which code to use, how to compare countries in one call, data cadence caveats, and where to go for adjacent domains. Nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes further by mapping natural-language topics to concrete indicator codes (GDP=NY.GDP.MKTP.CD, unemployment=SL.UEM.TOTL.ZS, etc.), which is meaning the schema's single example does not supply. It also restates the ";"-separated multi-country convention and the 8-code cap, though those are already in the schema, so it falls short of a full 5.

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?

Opens with a specific verb and resource ("Get World Bank time-series data, economic, social, and development statistics") and scopes it to "ANY country worldwide" with concrete examples. It explicitly distinguishes itself from siblings country_co2_emissions and get_governance_indicators, so an agent can route without opening schemas.

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?

Gives explicit when-to-use triggers in the form of literal user phrasings ("unemployment rate in <country>", "GDP of <country>"), plus explicit when-not-to-use routing to the CO2 and governance tools. It even documents a deprecated-code trap (EN.ATM.CO2E.* deleted) that would otherwise cause a failed call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.