who-gho-mcp-server

List WHO GHO Indicators

who_list_indicators

Read-onlyIdempotent

Browse the WHO Global Health Observatory indicator catalog with pagination. Use when you want to explore indicators without a keyword, or to page through the full catalog. Use who_search_indicators when you have a keyword to narrow the results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "who_list_indicators"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of indicators to return per page. Default 50, max 500.
`offset`	No	Zero-based offset for pagination. Default 0.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Requested and applied limit when the page was clamped.
`hasMore`	No	True when more indicators exist beyond the current page.
`pageInfo`	No	Human-readable page position, e.g. "offset 0, showing 50 of 3102". Use to construct the next offset.
`indicators`	No	Indicators for the requested page.
`totalCount`	No	Total number of indicators in the GHO catalog.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

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

addedOutput schema / properties / notice

Added value: +{
+  "description": "Requested and applied limit when the page was clamped.",
+  "type": "string"
+}

changedOutput schema / properties / pageInfo / description

Previous value: -"Human-readable page position, e.g. \"offset 0, showing 50 of 3059\". Use to construct the next offset."New value: +"Human-readable page position, e.g. \"offset 0, showing 50 of 3102\". Use to construct the next offset."

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": [
+      "indicators",
+      "totalCount",
+      "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.",
+          "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: -[
-  "indicators",
-  "totalCount",
-  "hasMore",
-  "pageInfo"
-]

Changed4 schema fields changedMay 30, 2026

addedOutput schema / properties / pageInfo

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

removedOutput schema / properties / total

Removed value: -{
-  "description": "Total number of indicators in the GHO catalog.",
-  "type": "number"
-}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total number of indicators in the GHO catalog.",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "indicators",
-  "total",
-  "hasMore"
-]New value: +[
+  "indicators",
+  "totalCount",
+  "hasMore",
+  "pageInfo"
+]

First observedMay 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety and idempotence are covered. The description adds that this is a paginated catalog browse, which is useful behavioral context beyond the 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?

Three short sentences, front-loaded with the core purpose and immediately followed by usage guidance and the alternative tool. No wasted text.

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, parameters are fully described in the schema, and the selection alternative is named. Everything an agent needs to choose and invoke this tool correctly is present.

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 limit and offset are fully documented in the schema. The description mentions pagination but adds no syntax or constraint details beyond what the schema already provides.

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: browsing the WHO Global Health Observatory indicator catalog. It also clarifies that this is the full-catalog browsing tool, which cleanly distinguishes it from keyword-based search.

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 this tool (exploring without a keyword, paging through the full catalog) and names the alternative sibling, who_search_indicators, for keyword narrowing.

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.