Country Stats Facts

Get a country statistic

get_country_indicator

Read-onlyIdempotent

Use this when the user asks for one official statistic for one country, such as "what is Vietnam's population?" or "what was unemployment in Spain in 2022?". Pass the country (name or ISO code), the indicator (population, gdp, gdp_per_capita, gdp_growth, inflation, unemployment, life_expectancy, fertility_rate, urban_population, internet_users, exports, gini, co2_per_capita, electricity_use) and optionally a year. Returns the value, its year and unit, the source and the date it was last updated; without a year it returns the latest year with data. It reads annual World Bank statistics only: no live data, forecasts or regions.

Input Schema

Name	Required	Description
`year`	No	A specific calendar year; leave out for the latest year with data
`country`	Yes	A country name or ISO code, such as "Vietnam", "VN" or "VNM"
`indicator`	Yes	population, gdp, gdp_per_capita, gdp_growth, inflation, unemployment, life_expectancy and the other listed series

Output Schema

Name	Required	Description
`year`	Yes
`as_of`	Yes	ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
`value`	Yes
`notice`	Yes
`source`	Yes	Who the data comes from, to cite and to check it against.
`status`	Yes
`country`	Yes
`message`	No
`indicator`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "country": "DE",
+    "indicator": "population"
+  }
+]

addedOutput schema / properties / as_of / description

Added value: +"ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch."

addedOutput schema / properties / source / description

Added value: +"Who the data comes from, to cite and to check it against."

addedOutput schema / properties / source / properties

Added value: +{
+  "name": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / source / required
```
Added value: +[
+  "name",
+  "url"
+]
```

changedOutput schema / properties / source / type

Previous value: -"string"New value: +"object"

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered; the description adds genuinely new behavior — the default-year fallback ('latest year with data'), the data vintage ('date it was last updated'), and the static-data caveat. It stops short of describing error/ambiguity handling for unrecognized country names, which is the one remaining gap for an open-world lookup.

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?

Front-loaded with the trigger condition and examples before logistics, and every sentence carries information. The inline re-listing of all fourteen indicators is somewhat redundant with the enum, costing a little density.

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 three-parameter read tool with a full schema, complete annotations and an output schema, the description covers trigger, inputs, default behavior, return shape and scope limits — everything needed to invoke it correctly without opening the 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 100%, so the baseline is 3; the description adds value by restating the indicator vocabulary as a discovery aid and clarifying that year is optional and defaults to the latest available year. The country param's name-or-ISO flexibility is only echoed from the schema rather than extended, keeping it below top marks.

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?

Names a specific verb+resource ('one official statistic for one country') and anchors it with two concrete user-question examples. It also draws a clear boundary against siblings by declaring it reads annual World Bank statistics only — no forecasts (get_imf_forecast) or regions.

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?

The opening 'Use this when the user asks for one official statistic for one country' plus the Vietnam/Spain examples give an explicit trigger condition, and the closing 'no live data, forecasts or regions' tells the agent when to route elsewhere. Both the positive and negative cases are stated.

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

All Country Stats Facts tools Inspect

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.