Skip to main content
Glama

worlduank

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Gdp

get_gdp
Read-onlyIdempotent

Fetch annual GDP in current USD (NY.GDP.MKTP.CD) 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 GDP data in current USD 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 GDP data in current USD sorted by year descending",
+      "items": {
+        "properties": {
+          "value": {
+            "description": "GDP value in current USD 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": "DE"
+  }
+]
  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 establish read-only, open-world, idempotent, non-destructive behavior. The description adds concrete behavioral context: data source (World Bank), units (current USD), default date range (2015–2024), return format (year-by-year array), and the indicator code. This enriches the tool's behavior beyond the safety annotations.

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?

Two concise sentences, front-loaded with the action and resource. The secondary sentence covers default range, output format, and relationship to a sibling tool without extraneous wording.

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 single-parameter tool with an output schema, the description is remarkably complete: it specifies data source, units, default period, output structure, and the tool's relationship to get_indicator. No significant behavioral aspect is 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?

The schema provides 100% coverage for the single required parameter, country_code, with a clear ISO code description. The description does not add syntactical detail, but it reinforces that the tool operates per country. Since schema description coverage is high, a baseline of 3 is appropriate.

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?

Description uses specific verb 'Fetch', names the exact indicator (GDP in current USD, NY.GDP.MKTP.CD), the data source (World Bank), and the default date range. It explicitly distinguishes from the broader get_indicator by labeling itself a shortcut.

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 states it is a 'Shortcut for get_indicator', providing a clear alternative and implicit guidance on when to use this tool (for GDP data) versus the general indicator tool. However, it doesn't explicitly list exclusion criteria or contrast with other sibling tools like get_population.

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