Skip to main content
Glama

Stratalize Intelligence

Get World Bank Country Indicators

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.8/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 5-year trend and direction in the return, coverage of 200+ countries and 1,400+ indicators, quarterly update cadence, data source, and a per-call cost of $0.10 USDC. It does not cover behavior for missing/suppressed country-indicator pairs.

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?

The use-case clause is well front-loaded, but the Brazil worked example runs several sentences and largely restates what the indicator list already conveyed, and the coverage/source/price sentences are stacked at the tail. It is informative but could be trimmed by roughly a third without losing actionable content.

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?

For a two-parameter read tool with no output schema, the description covers scope, return shape (trend + direction), data freshness, coverage, and cost — enough to call it confidently and budget for it. The main residual gap is what happens when an indicator is unavailable for a country or year.

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 is documented in-schema and the indicator enum is self-describing. The description names six of the nine enum indicators, implicitly clarifying what each represents, but adds no format, defaulting, or error semantics for the remaining values (trade_pct_gdp, gini_coefficient, gdp_growth).

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 resource (World Bank development indicators) and enumerates the returned metrics (GDP, inflation, unemployment, ease of doing business, government debt, FDI inflows), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with the many benchmark-style siblings, but the country-macro scope is unmistakable.

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?

It opens with concrete triggering scenarios — country risk for expansion, foreign market evaluation, economic trajectory benchmarking, ESG country scoring — which gives clear when-to-use context. There are no explicit exclusions or named alternative tools, so it stops short of full routing guidance.

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