Skip to main content
Glama
Sign In
Globalpulse-MCP

Globalpulse-MCP

by gpavan1992
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

World Bank — Get Country Indicator

globalpulse_worldbank_get_indicator
Read-onlyIdempotent

Retrieve World Bank macroeconomic indicators for any country, covering GDP, inflation, unemployment, trade, debt, and more. Data from 1960 to present.

Instructions

Fetch World Bank macroeconomic indicator data for any country. Covers GDP, inflation, unemployment, trade, debt, population, poverty. 10,000+ indicators from 1960–present.

Common codes: NY.GDP.MKTP.CD (GDP), FP.CPI.TOTL.ZG (inflation), SL.UEM.TOTL.ZS (unemployment), SP.POP.TOTL (population), NE.TRD.GNFS.ZS (trade % GDP).

Args:

  • country_code: ISO alpha-2 or alpha-3 (e.g. "IN", "US", "BRA")

  • indicator: World Bank indicator code

  • start_year: Start year (default 2000)

  • end_year: End year (default current year)

  • response_format: "markdown" or "json"

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": "globalpulse_worldbank_get_indicator"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_yearNo
indicatorYesWorld Bank indicator code e.g. "NY.GDP.MKTP.CD"
start_yearNo
country_codeYesISO code e.g. "IN", "US"
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false, so the description needs only to add context. It adds value by detailing data scope (10,000+ indicators, 1960–present) and examples, without contradicting annotations. No mention of rate limits or pagination, but acceptable for a read-only tool.

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 description is moderately sized with a front-loaded purpose statement. It uses bullet points within text and a clear Args list. Some redundancy (e.g., date range repeated), but overall efficient and well-structured.

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?

Given the complexity of 5 parameters, 2 required, and no output schema, the description covers the tool's purpose, parameter details, and data scope. It provides enough context for an agent to use the tool effectively, though lacking return format details (acceptable without output schema).

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 40% (only country_code and indicator have descriptions). The description compensates by explaining all parameters: country_code format, indicator as 'World Bank indicator code', start_year/end_year defaults and ranges, and response_format options. It adds meaning beyond the schema, especially for parameters without schema descriptions.

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?

The description clearly states 'Fetch World Bank macroeconomic indicator data for any country', specifying the verb (Fetch), resource (World Bank macroeconomic indicator data), and scope (any country). It also lists example indicators and a date range, distinguishing it from sibling tools like list_indicators or weather/disasters tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides common indicator codes and explains the tool's data coverage, implying when to use it. However, it does not explicitly state when not to use or mention alternatives like globalpulse_worldbank_list_indicators for finding indicator codes, which would help an agent decide.

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

Deploy Server

Other Tools