who-gho-mcp-server

Search WHO GHO Indicators

who_search_indicators

Read-onlyIdempotent

Search the WHO Global Health Observatory indicator catalog by words in the indicator name. Every whitespace-separated word must match independently as a case-insensitive substring, in any order; try "tuberculosis incidence", "sanitation basic", or "HIV". When no names match, an exact indicator-code lookup is attempted. Returns canonical indicator codes and names for who_query_indicator_data. Refine the query or page through the same result set 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": {
      "query": "<query>"
    },
    "name": "who_search_indicators"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of indicators to return. Default 20, max 100.
`query`	Yes	Words to match independently in indicator names, or an exact indicator code.
`offset`	No	Zero-based offset into the matches for this query. Default 0. Read hasMore and nextOffset from the response to continue paging. An offset at or beyond totalCount returns an empty indicators array, not an error.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Present when matches were withheld or the requested offset ran past the end of the result set. Explains how to reach the remaining matches.
`offset`	No	Zero-based offset this page started at.
`hasMore`	No	True when more matches remain beyond this page. Pair with nextOffset to continue.
`pageInfo`	No	Human-readable page position, e.g. "offset 0, showing 20 of 3003". Use to construct the next offset.
`indicators`	No	Matching indicators up to the requested limit.
`nextOffset`	No	Offset to request for the next page. Absent when this page reached the end of the matches.
`totalCount`	No	Total indicators matching the query in the catalog, before the limit is applied.
`effectiveQuery`	No	Keyword used for the catalog search, as received by the server.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

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

changedInput schema / properties / query / description

Previous value: -"Keyword to search in indicator names, e.g. \"life expectancy\" or \"tuberculosis\"."New value: +"Words to match independently in indicator names, or an exact indicator code."

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

Previous value: -"Machine-readable failure mode. Declared by this tool: `no_results`: No indicators matched the query keyword. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `no_results`: No indicator names matched every search word and no exact indicator code resolved. 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": [
+      "indicators",
+      "effectiveQuery",
+      "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: `no_results`: No indicators matched the query keyword. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "no_results"
+          ],
+          "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",
-  "effectiveQuery",
-  "totalCount",
-  "offset",
-  "hasMore",
-  "pageInfo"
-]

Changed7 schema fields changedAug 18, 2026

addedInput schema / properties / offset

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

addedOutput schema / properties / hasMore

Added value: +{
+  "description": "True when more matches 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 matches.",
+  "type": "number"
+}

changedOutput schema / properties / notice / description

Previous value: -"Present when the limit was reached and more results exist. Suggests how to get additional results."New value: +"Present when matches were withheld or the requested offset ran past the end of the result set. Explains how to reach the remaining matches."

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 20 of 3003\". Use to construct the next offset.",
+  "type": "string"
+}

changedOutput schema / required

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

Changed6 schema fields changedMay 30, 2026

addedOutput schema / properties / effectiveQuery

Added value: +{
+  "description": "Keyword used for the catalog search, as received by the server.",
+  "type": "string"
+}

removedOutput schema / properties / note

Removed value: -{
-  "description": "Present when the limit was reached and more results exist. Suggests how to get additional results.",
-  "type": "string"
-}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Present when the limit was reached and more results exist. Suggests how to get additional results.",
+  "type": "string"
+}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total indicators matching the query in the catalog, before the limit is applied.",
+  "type": "number"
+}

removedOutput schema / properties / totalMatches

Removed value: -{
-  "description": "Total count of indicators matching the query, before the limit is applied.",
-  "type": "number"
-}

changedOutput schema / required

Previous value: -[
-  "indicators",
-  "totalMatches"
-]New value: +[
+  "indicators",
+  "effectiveQuery",
+  "totalCount"
+]

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 cover read-only/idempotent safety; the description adds genuinely non-obvious behavior: AND-semantics across whitespace-separated words, case-insensitive substring matching, in-any-order, and a silent fallback to exact code lookup. It also notes that paging past the end yields an empty array rather than an error.

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?

Every sentence carries information: matching rule first, examples second, fallback third, return value and paging last. No filler or repetition of schema 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, so return shape need not be spelled out, yet the description still tells the agent what it gets (canonical codes and names) and how to continue paging — complete for a 3-parameter search tool.

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 3 is the floor; the description earns more by explaining the matching rule for 'query' and how 'offset' reuses the same result set, which the schema only alludes to.

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 ('search the WHO Global Health Observatory indicator catalog') and immediately names the downstream consumer (who_query_indicator_data), which separates it from the listing/metadata siblings.

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?

Gives concrete query examples and explains the fallback path (exact code lookup) plus when to refine or page. It never explicitly contrasts with who_list_indicators or who_get_indicator_metadata, so an agent still has to infer when to prefer those.

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.