Skip to main content
Glama

get_world_bank_country_indicators

Read-only

Use when assessing country risk for international expansion, evaluating a foreign market for investment or partnership, benchmarking a country's economic trajectory for capital allocation decisions, or producing ESG country-level scoring. Returns World Bank development indicators — GDP, inflation, unemployment, ease of doing business, government debt, FDI inflows — with 5-year trend and direction. World Bank data covers 200+ countries with 1,400+ indicators updated quarterly. Example: Brazil — GDP growth 2.9% (2023), inflation declining from 9.3% to 4.6%, ease of doing business ranked 124th globally, net FDI inflows $65.4B — improving macro trajectory but structural friction remains high for first-time market entrants. Source: World Bank Open Data. $0.10 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country_code": "<country_code>",
      "indicator": "<indicator>"
    },
    "name": "get_world_bank_country_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
indicatorYes
country_codeYesISO 3166-1 alpha-2 or alpha-3 country code (e.g. BR, DEU, JP, US, GB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is fully covered without the description's help. The description does add genuinely useful non-annotation context — quarterly refresh cadence, 200+ country / 1,400+ indicator coverage, World Bank Open Data as source, and a $0.10 USDC per-call price — which is real value beyond the structured fields.

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

Conciseness4/5

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

The structure is well front-loaded: use cases first, then what is returned, then coverage, then an example, then source and price. The Brazil example runs long and slips into interpretive commentary ('structural friction remains high for first-time market entrants'), which is illustrative but heavier than needed for a definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so adequately by stating that indicators come with a 5-year trend and direction. Coverage, freshness, source, and cost are all disclosed; only the precise per-indicator payload shape and error behavior for invalid country/indicator combinations are left unstated.

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 coverage is 50%: country_code carries its own format description while the indicator enum has no per-value documentation. The description partially compensates by listing six of the nine indicator values and the Brazil example demonstrates real usage, but it omits trade_pct_gdp and gini_coefficient and says nothing about units or comparison semantics for the returned trend.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource explicitly: it 'Returns World Bank development indicators' and enumerates the indicator families (GDP, inflation, unemployment, ease of doing business, government debt, FDI inflows) plus a 5-year trend. It is unquestionably a macro country-data tool rather than a company or market instrument tool, though it never names a sibling to contrast against.

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?

Four concrete triggering scenarios are given (country risk for expansion, foreign-market evaluation, economic trajectory benchmarking, ESG country scoring), which tells the agent exactly what question shapes this tool answers. There is no when-not-to-use guidance and no named alternative for adjacent needs, so it stops short of a 5.

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.

Resources