Skip to main content
Glama

Primary Sources

by io.github.simonmak-ascent
OverviewDiscussionsAdmin

world_bank_indicator

Read-onlyIdempotent

Fetch a World Bank development-indicator time series for one country (free, no key). Returns year/value observations for an indicator such as GDP or population. Use for long-run country macro data; use fred_series for US/global economic series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate range, e.g. 2015:2025
countryYesISO country code, e.g. HK or US
perPageNoObservations per page, default 5
indicatorYesWorld Bank indicator code, e.g. NY.GDP.MKTP.CD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesSource payload; fields vary per tool
sourceYesHuman-readable upstream source name
retrievedAtYesISO-8601 timestamp of retrieval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"ISO country code, e.g. HK or US"
    • changedInput schema / properties / date / description
      Previous value: -"e.g. 2015:2025"New value: +"Date range, e.g. 2015:2025"
    • addedInput schema / properties / indicator / description
      Added value: +"World Bank indicator code, e.g. NY.GDP.MKTP.CD"
    • addedInput schema / properties / perPage / description
      Added value: +"Observations per page, default 5"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Source payload; fields vary per tool",
+      "type": "object"
+    },
+    "retrievedAt": {
+      "description": "ISO-8601 timestamp of retrieval",
+      "type": "string"
+    },
+    "source": {
+      "description": "Human-readable upstream source name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "retrievedAt",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful context beyond them: the source requires no API key ('free, no key') and the return format is year/value observations. It stops short of mentioning pagination behavior despite a perPage parameter, so it is not fully rich.

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?

Three tight sentences, front-loaded with the action and resource, then the return shape, then the routing rule. Every sentence carries distinct information with no waste.

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?

With a fully documented schema, an output schema, and annotations covering the safety profile, the description only needed to add purpose, auth context, and sibling routing — all of which it does. An agent has everything required to call it 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?

Schema description coverage is 100%, so all four parameters (date range, ISO country code, perPage, indicator code) are already documented. The description reinforces scope ('for one country', 'an indicator such as GDP or population') but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Fetch a World Bank development-indicator time series for one country') plus the shape of the result ('year/value observations'). It also names the sibling fred_series as the contrasting tool, so an agent can distinguish them without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('long-run country macro data') and names the alternative plus the condition that selects it ('use fred_series for US/global economic series'). Nothing is left to inference.

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

All Primary Sources 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