Skip to main content
Glama

worlduank

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Population

get_population
Read-onlyIdempotent

Fetch annual total population (SP.POP.TOTL) for a country from the World Bank, defaulting to 2015–2024. Returns a year-by-year array of values. Shortcut for get_indicator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesISO country code (e.g., "US", "GBR", "CN")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTime-series population data 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
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "country": {
+      "description": "Country name or code",
+      "type": "string"
+    },
+    "country_id": {
+      "description": "World Bank country ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "data": {
+      "description": "Time-series population data sorted by year descending",
+      "items": {
+        "properties": {
+          "value": {
+            "description": "Total population value for the year",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Year of the observation",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "date_range": {
+      "description": "Requested date range in start:end format",
+      "type": "string"
+    },
+    "indicator_id": {
+      "description": "World Bank indicator code",
+      "type": "string"
+    },
+    "indicator_name": {
+      "description": "Full indicator name/description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_updated": {
+      "description": "Last update timestamp from World Bank API",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total_records": {
+      "description": "Total number of records available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "country",
+    "country_id",
+    "indicator_id",
+    "indicator_name",
+    "date_range",
+    "total_records",
+    "last_updated",
+    "data"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country_code": "BR"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, open-world, idempotent, and non-destructive. The description adds useful behavioral context such as the default time range and the output array format, which go beyond the annotations. It doesn't mention rate limits or errors, but the annotations cover the main safety profile.

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

Conciseness5/5

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

The description is three concise sentences, each with a distinct purpose: core action, return format, and relationship to get_indicator. It is front-loaded with the most important information and contains no unnecessary words.

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?

For a simple 1-parameter tool, the description fully covers purpose, default behavior, output format, and its relationship to sibling tools. The output schema exists, so return values don't need further explanation, and the description is sufficient for an agent to select and invoke the tool correctly.

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?

The schema covers 100% of parameters with a single 'country_code' parameter fully described. The description doesn't add additional parameter-level semantics beyond what's in the schema, so the baseline of 3 is appropriate given the high schema coverage.

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 the tool fetches annual total population (SP.POP.TOTL) from the World Bank, using a specific verb and resource. It also explicitly distinguishes itself from the generic get_indicator tool by noting it's a shortcut, making its purpose unambiguous.

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?

The description provides clear context by specifying the default date range (2015–2024) and the return format (year-by-year array). The 'Shortcut for get_indicator' line indicates when to use this tool instead of the generic alternative, though it doesn't explicitly state exclusions or alternatives beyond that.

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

All worlduank toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources