who-gho-mcp-server

List GHO Dimension Values

who_list_dimension_values

Read-onlyIdempotent

List valid codes and labels for a WHO GHO dimension type such as COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, or AGEGROUP. Use this to discover valid filter values before calling who_query_indicator_data, or to confirm the WHO code for a country, including historical codes. Use who_list_dimensions to discover all available dimension type codes. Results are paged in a deterministic order — narrow hierarchical dimensions with parent_code (e.g. the countries in one WHO region), and page the rest with offset.

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": {
      "dimension": "<dimension>"
    },
    "name": "who_list_dimension_values"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of values to return per page. Default 100, max 500.
`offset`	No	Zero-based offset into the values for this dimension and filter. Default 0. Read hasMore and nextOffset from the response to continue paging. An offset at or beyond totalCount returns an empty values array, not an error.
`dimension`	Yes	Dimension type code. Use who_list_dimensions to discover all available codes. Common values: COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, AGEGROUP.
`parent_code`	No	Restrict results to values under one parent, e.g. dimension="COUNTRY" with parent_code="EUR" for the countries in the WHO European Region. Only hierarchical dimensions carry a parent; a filter that matches nothing returns an empty page for a valid dimension, not an error.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Present when values were withheld, the parent_code filter matched nothing, or the requested offset ran past the end. Explains what to do next.
`offset`	No	Zero-based offset this page started at.
`values`	No	Valid values for this dimension type, for the requested page.
`hasMore`	No	True when more values remain beyond this page. Pair with nextOffset to continue.
`pageInfo`	No	Human-readable page position, e.g. "offset 0, showing 100 of 234". Use to construct the next offset.
`dimension`	No	The requested dimension type code.
`nextOffset`	No	Offset to request for the next page. Absent when this page reached the end of the values.
`totalCount`	No	Total values for this dimension and filter, before the limit is applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

removedInput schema / properties / limit / maximum
```
Removed value: -500
```

changedInput schema / properties / parent_code / description

Previous value: -"Restrict results to values under one parent, e.g. dimension=\"COUNTRY\" with parent_code=\"EUR\" for the countries in the WHO European Region. Only hierarchical dimensions carry a parent; a filter that matches nothing returns an empty page, not an error."New value: +"Restrict results to values under one parent, e.g. dimension=\"COUNTRY\" with parent_code=\"EUR\" for the countries in the WHO European Region. Only hierarchical dimensions carry a parent; a filter that matches nothing returns an empty page for a valid dimension, not an error."

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `dimension_not_found`: An unfiltered lookup of the dimension code returned no values at all — it does not exist in the GHO catalog. `malformed_identifier`: dimension carries an unpaired UTF-16 surrogate, so it cannot be encoded into the request URL. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `dimension_not_found`: An unfiltered lookup returned no values, or a filtered empty result was confirmed absent by the dimension metadata endpoint. `malformed_identifier`: dimension carries an unpaired UTF-16 surrogate, so it cannot be encoded into the request URL. Other values are possible when a failure originates below the handler."

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "dimension",
+      "values",
+      "totalCount",
+      "offset",
+      "hasMore",
+      "pageInfo"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `dimension_not_found`: An unfiltered lookup of the dimension code returned no values at all — it does not exist in the GHO catalog. `malformed_identifier`: dimension carries an unpaired UTF-16 surrogate, so it cannot be encoded into the request URL. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "dimension_not_found",
+            "malformed_identifier"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "dimension",
-  "values",
-  "totalCount",
-  "offset",
-  "hasMore",
-  "pageInfo"
-]

Changed11 schema fields changedAug 18, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 100,
+  "description": "Number of values to return per page. Default 100, max 500.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based offset into the values for this dimension and filter. Default 0. Read hasMore and nextOffset from the response to continue paging. An offset at or beyond totalCount returns an empty values array, not an error.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / parent_code

Added value: +{
+  "description": "Restrict results to values under one parent, e.g. dimension=\"COUNTRY\" with parent_code=\"EUR\" for the countries in the WHO European Region. Only hierarchical dimensions carry a parent; a filter that matches nothing returns an empty page, not an error.",
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / hasMore

Added value: +{
+  "description": "True when more values remain beyond this page. Pair with nextOffset to continue.",
+  "type": "boolean"
+}

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "Offset to request for the next page. Absent when this page reached the end of the values.",
+  "type": "number"
+}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Present when values were withheld, the parent_code filter matched nothing, or the requested offset ran past the end. Explains what to do next.",
+  "type": "string"
+}

addedOutput schema / properties / offset

Added value: +{
+  "description": "Zero-based offset this page started at.",
+  "type": "number"
+}

addedOutput schema / properties / pageInfo

Added value: +{
+  "description": "Human-readable page position, e.g. \"offset 0, showing 100 of 234\". Use to construct the next offset.",
+  "type": "string"
+}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total values for this dimension and filter, before the limit is applied.",
+  "type": "number"
+}

changedOutput schema / properties / values / description

Previous value: -"Valid values for this dimension type."New value: +"Valid values for this dimension type, for the requested page."

changedOutput schema / required

Previous value: -[
-  "dimension",
-  "values"
-]New value: +[
+  "dimension",
+  "values",
+  "totalCount",
+  "offset",
+  "hasMore",
+  "pageInfo"
+]

First observedMay 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds behavior beyond the readOnly/idempotent annotations: deterministic result ordering, the parent_code narrowing strategy for hierarchical dimensions, and historical codes being returned. The 'offset at or beyond totalCount returns an empty page' point duplicates the schema's offset description rather than adding new information, which keeps this just under a 5.

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?

Purpose is front-loaded in the first sentence, followed by usage and paging guidance with no filler. The final paging sentence is dense, packing ordering, hierarchy handling, and offset paging into one clause, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description still names hasMore/nextOffset continuation. For a 4-parameter, read-only paged lookup, everything an agent needs to select and invoke it correctly is present.

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 earns a bump by explaining when to use parent_code versus offset paging, which is a usage strategy the schema does not state. The parent_code example (EUR for the European Region) mirrors the schema text, so it adds little on its own.

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?

Starts with a specific verb and resource: 'List valid codes and labels for a WHO GHO dimension type', then enumerates the concrete code families (COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, AGEGROUP). It is clearly differentiated from who_list_dimensions (dimension types) and who_query_indicator_data (data retrieval), so an agent can pick it without opening a 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?

Gives explicit when-to-use: discover filter values before calling who_query_indicator_data, or confirm a country code including historical ones. It also routes the agent to who_list_dimensions for discovering dimension type codes and states the narrowing-vs-paging strategy for hierarchical dimensions.

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

All who-gho-mcp-server 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.