who-gho-mcp-server

Name: who-gho-mcp-server
Author: cyanheads

Server Details

WHO Global Health Observatory — 3,102 indicators across 194 member states.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 83 days
Last Tested: 2026-11-08 05:40
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: cyanheads/who-gho-mcp-server
GitHub Stars: 3
Server Listing: @cyanheads/who-gho-mcp-server
ChatGPT: –
Claude: –

TDQS

A4.6/5.0

Scored 2026-10-26 08:05 across 6 tools

Disambiguation5/5

Each tool has a distinct role in the discovery-to-query workflow: catalog browsing, search, indicator metadata, dimension discovery, dimension value lookup, and data querying. The descriptions explicitly clarify boundaries, such as when to use who_list_indicators versus who_search_indicators and how metadata differs from querying.

Naming Consistency5/5

All tool names follow a consistent who_<verb>_<noun> snake_case pattern, with clear verbs such as get, list, search, and query. The convention is predictable across all six tools.

Tool Count5/5

Six tools are well-scoped for a read-only WHO GHO API server: each covers a necessary step in discovering indicators, validating dimensions, and fetching data. There are no redundant or trivial tools.

Completeness5/5

The tool surface covers the full read-only lifecycle: browsing and searching indicators, inspecting indicator metadata, listing dimension types and values, and querying indicator data with filters and pagination. No obvious CRUD-style gaps apply because the domain is data retrieval, and the find-then-query workflow is fully supported.

Available Tools

6 tools

who_get_indicator_metadataGet WHO GHO Indicator MetadataA

Read-onlyIdempotent

Inspect

Fetch metadata for WHO GHO indicator codes: the canonical code, full name, and supported dimensions (e.g. COUNTRY, REGION, SEX, YEAR, WORLDBANKINCOMEGROUP, AGEGROUP). Call this before who_query_indicator_data to confirm valid filter dimensions. Processes the first 10 entries and returns unprocessedCodes to submit next, accepting at most 1000 raw entries. With GHO_CLAMP_LIMITS=false, calls above 10 reject. Many valid indicators have no dimension listing upstream — those return an empty dimensions array with dimensionsNote. Processed codes absent from both the catalog and dimension table appear in notFound. No found entries raises all_not_found only when no unprocessed entries remain.

Name	Required	Description	Default
`indicator_codes`	Yes	Indicator codes, e.g. ["WHOSIS_000001", "MDG_0000000026"]. Processes the first ten and returns remaining entries for the next call; at most 1000 entries.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notFound`	No	Indicator codes that resolved to neither a catalog name nor any dimension rows — they do not exist in the GHO catalog.
`indicators`	No	Metadata for each code that resolved to a catalog entry or dimension rows.
`unprocessedCodes`	No	Remaining request entries in their original order. Submit these codes next.

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses batching (first 10 processed, unprocessedCodes returned), the 1000-entry cap, the GHO_CLAMP_LIMITS=false rejection behavior above 10, empty dimensions arrays with dimensionsNote, notFound routing, and the all_not_found condition. That is unusually rich operational context for a read tool.

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?

The purpose and the 'call before' directive are front-loaded, and each subsequent sentence covers a distinct edge case (clamping, missing dimensions, notFound, all_not_found). The latter half is dense and edge-case heavy, but no sentence is truly wasted for correct invocation.

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 one-parameter read tool with full annotations and an output schema, the description covers everything an agent needs: what it returns, how to iterate with unprocessedCodes, and how to interpret empty dimensions, notFound, and all_not_found. Some return-shape detail duplicates the output schema, but nothing essential is missing.

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% and the schema already documents the array and its limits, so the description could rest on baseline 3. It adds marginal value by tying the parameter to the clamping behavior and the returned unprocessedCodes, though most of this overlaps the schema's own parameter text.

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 (Fetch) and resource (metadata for WHO GHO indicator codes) and enumerates exactly what is returned: canonical code, full name, supported dimensions. It is clearly distinguishable from the query/list siblings by naming who_query_indicator_data as the downstream consumer.

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?

Explicitly says 'Call this before who_query_indicator_data to confirm valid filter dimensions,' giving a clear placement in the workflow. It also warns that many valid indicators lack upstream dimension listings, which pre-empts a common misinterpretation, but it does not contrast against who_list_dimensions or who_search_indicators.

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

who_list_dimensionsList GHO Dimension TypesA

Read-onlyIdempotent

Inspect

List all dimension type codes and human-readable titles available in the WHO Global Health Observatory API. Use this to discover valid dimension codes before calling who_list_dimension_values. Common dimensions include COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, and AGEGROUP, but many additional types exist — this tool exposes them all.

Name	Required	Description	Default
No parameters

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`dimensions`	No	All available dimension types in the GHO catalog.

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already carry readOnlyHint=true and idempotentHint=true, so the safety profile is covered by structured data. The description adds one useful behavioral signal — 'this tool exposes them all' — indicating the response is the complete set of dimensions rather than a paginated or filtered subset. This is helpful context but not extensive.

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?

Three sentences, all earning their place: the main purpose is front-loaded, the workflow guidance follows, and the examples close it out. Nothing is wasted, and the structure is scannable.

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 zero-parameter, read-only list tool with an output schema present and safety annotations provided, the description covers everything an agent needs: what it returns, how to use it in context, and what to expect. Nothing material is missing.

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?

The tool takes zero parameters and the schema is an empty object, so the baseline of 4 applies. There are no parameter semantics for the description to clarify, and it does not attempt to invent any.

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?

The description states a specific verb (List) with an explicit resource (dimension type codes and human-readable titles) scoped to the WHO GHO API. It also clarifies the tool's role in the discovery workflow and gives concrete examples (COUNTRY, REGION, SEX), making it immediately distinguishable from siblings like who_list_indicators.

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?

Explicit guidance is given: 'Use this to discover valid dimension codes before calling who_list_dimension_values,' which pins down the tool's position in the expected workflow and names the downstream sibling. It lacks an explicit 'when not to use' statement, hence not a full 5.

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

who_list_dimension_valuesList GHO Dimension ValuesA

Read-onlyIdempotent

Inspect

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.

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.

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.

who_list_indicatorsList WHO GHO IndicatorsA

Read-onlyIdempotent

Inspect

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.

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.

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.

who_query_indicator_dataQuery WHO GHO Indicator DataA

Read-onlyIdempotent

Inspect

Query data rows for a single WHO GHO indicator with optional spatial, temporal, and dimension filters. Returns rows with numeric values, uncertainty intervals (Low/High), and spatial/time metadata. This is the primary data-fetching tool in the find-then-query workflow: use who_search_indicators to find the indicator code, optionally call who_get_indicator_metadata to confirm which filter dimensions are valid, then call this tool. Discover positional filters from returned dim1Type/dim1, dim2Type/dim2 and dim3Type/dim3 pairs; metadata alone does not identify a slot. Spatial filters are mutually exclusive per call: provide only one of country_codes, region_codes, or income_group_codes — mixing them triggers an error. Omitting all spatial filters returns all geographies (may be large; use limit to cap). The sex filter only applies when the indicator uses SEX as its first cross-cutting dimension — if not, the filter returns empty rows; check who_get_indicator_metadata first if uncertain. Rows are returned in a deterministic order (most recent first by default), so a capped result is the top of a defined slice rather than an arbitrary sample; page through the rest with offset.

Name	Required	Description	Default
`sex`	No	Filter on sex dimension: SEX_BTSX (both sexes), SEX_FMLE (female), SEX_MLE (male). Only applies when the indicator uses SEX as its first cross-cutting dimension.
`sort`	No	Row ordering: "year_desc" (default) returns the most recent years first, "year_asc" the earliest first. Ties are broken by spatial code, then dimension, then row id.	year_desc
`limit`	No	Maximum number of data rows to return. Default 200, max 1000.
`offset`	No	Zero-based row offset for pagination. Default 0. Pages are stable because rows are returned in a deterministic order — read hasMore and nextOffset from the response to continue. An offset at or beyond totalRows returns an empty rows array, not an error.
`year_to`	No	End year (inclusive) for the time range filter, e.g. 2023.
`year_from`	No	Start year (inclusive) for the time range filter, e.g. 2015.
`dim1_value`	No	Value filter for indicators whose first cross-cutting dimension is not SEX (e.g. an AGEGROUP code like "YEARS05-14"). Ignored when sex is also provided.
`dim2_value`	No	Value filter for the second cross-cutting dimension, e.g. AGEGROUP_DAYS0-27. Discover the position from returned dim2Type/dim2 pairs; metadata does not identify the slot. Empty strings are ignored with a notice.
`dim3_value`	No	Value filter for the third cross-cutting dimension, e.g. CHILDCAUSE_CH9. Discover the position from returned dim3Type/dim3 pairs; metadata does not identify the slot. Empty strings are ignored with a notice.
`region_codes`	No	WHO region codes to filter on, e.g. ["AFR","EUR","AMR","EMR","SEAR","WPR"]. Returns the aggregate row for each named WHO region. To get country-level data for a region, use who_list_dimension_values with dimension="COUNTRY" and parent_code set to the region code to retrieve WHO country codes, then pass those to country_codes. Use who_list_dimension_values with dimension="REGION" to see all valid region codes. Mutually exclusive with country_codes and income_group_codes.
`country_codes`	No	WHO country codes to filter on, e.g. ["JPN","USA","BRA"], including historical codes such as ME1 and SDN736. Discover codes with who_list_dimension_values dimension="COUNTRY". Mutually exclusive with region_codes and income_group_codes.
`indicator_code`	Yes	Indicator code to query, e.g. "WHOSIS_000001". Use who_search_indicators to find codes.
`income_group_codes`	No	World Bank income group codes, e.g. ["WB_HI","WB_LMI","WB_LI","WB_UMI"]. Use who_list_dimension_values with dimension="WORLDBANKINCOMEGROUP" to see all valid codes. Mutually exclusive with country_codes and region_codes.
`include_uncertainty`	No	Include Low and High uncertainty interval bounds in output. Default true.

Output Schema

Name	Required	Description
`rows`	No	Data rows matching the query.
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Present when rows were withheld or the requested offset ran past the end of the result set. Explains how to reach the remaining rows.
`offset`	No	Zero-based row offset this page started at.
`hasMore`	No	True when rows remain beyond this page. Pair with nextOffset to continue.
`pageInfo`	No	Human-readable page position, e.g. "offset 0, showing 200 of 12936". Use to construct the next offset.
`totalRows`	No	Total row count matching the query on the server (before the limit is applied).
`truncated`	No	True when the result was capped at the requested limit.
`nextOffset`	No	Offset to request for the next page. Absent when this page reached the end of the result set.
`totalCount`	No	Alias of totalRows for cross-tool consistency — total rows before the limit.
`appliedFilters`	No	Filters that were applied to the query.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/closed-world, and the description adds real behavioral context beyond them: mixing spatial filters triggers an error, omitting all spatial filters returns all geographies and may be large, the sex filter can silently return empty rows, offset beyond totalRows returns an empty array rather than an error, and row order is deterministic so capped results are a defined slice. This is exactly the kind of edge-case disclosure annotations cannot convey.

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 purpose, then workflow, then constraint warnings, then pagination. It is dense but multi-sentence and slightly long, with a couple of points that overlap the schema's own parameter descriptions, though nothing is wasted filler.

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 14 parameters, an output schema, and full annotations, this description covers what an agent needs: entry workflow, filter-conflict rules, empty-result traps, determinism and paging semantics. Return values are only summarized as needed because an output schema exists.

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 still adds value beyond the schema by explaining cross-parameter interactions: the effect of providing no spatial filter, the conditional applicability of the sex filter, and the need to discover dim slot positions from returned dim pairs rather than metadata. Remaining specifics (limit max, enum meanings) are left to the schema, which is appropriate.

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 (query data rows) and resource (single WHO GHO indicator) with scope qualifiers. It explicitly positions itself as 'the primary data-fetching tool in the find-then-query workflow', which cleanly separates it from the sibling search, metadata, and dimension-listing tools.

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 an explicit ordered workflow (who_search_indicators -> who_get_indicator_metadata -> this tool), states exclusions (spatial filter family is mutually exclusive), and warns when the sex filter returns empty rows plus how to verify first. Alternatives and preconditions are named, not inferred.

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

who_search_indicatorsSearch WHO GHO IndicatorsA

Read-onlyIdempotent

Inspect

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.

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.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesOct 26, 2026

Changedwho_get_indicator_metadata7 fields changed

changedInput schema / properties / indicator_codes / description

Previous value: -"One to ten indicator codes, e.g. [\"WHOSIS_000001\", \"MDG_0000000026\"]."New value: +"Indicator codes, e.g. [\"WHOSIS_000001\", \"MDG_0000000026\"]. Processes the first ten and returns remaining entries for the next call; at most 1000 entries."

changedInput schema / properties / indicator_codes / maxItems
```
Previous value: -10New value: +1000
```

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

Previous value: -"Machine-readable failure mode. Declared by this tool: `all_not_found`: No requested indicator code resolved to a catalog entry. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `all_not_found`: No processed indicator code resolved and no unprocessed codes remain. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / indicators / description

Previous value: -"Metadata for each code that resolved to a catalog entry."New value: +"Metadata for each code that resolved to a catalog entry or dimension rows."

changedOutput schema / properties / indicators / items / properties / indicatorCode / description

Previous value: -"Indicator code."New value: +"Canonical catalog code when resolved; otherwise the requested dimension-only code."

changedOutput schema / properties / indicators / items / properties / indicatorName / description

Previous value: -"Full indicator name as returned by the GHO catalog."New value: +"Decoded catalog name; the code itself when only dimension metadata resolves."

addedOutput schema / properties / unprocessedCodes

Added value: +{
+  "description": "Remaining request entries in their original order. Submit these codes next.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changedwho_list_dimension_values3 fields changed

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."

Changedwho_list_indicators3 fields changed

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."

Changedwho_query_indicator_data9 fields changed

changedInput schema / properties / country_codes / description

Previous value: -"ISO 3166-1 alpha-3 country codes to filter on, e.g. [\"JPN\",\"USA\",\"BRA\"]. Mutually exclusive with region_codes and income_group_codes."New value: +"WHO country codes to filter on, e.g. [\"JPN\",\"USA\",\"BRA\"], including historical codes such as ME1 and SDN736. Discover codes with who_list_dimension_values dimension=\"COUNTRY\". Mutually exclusive with region_codes and income_group_codes."

addedInput schema / properties / dim2_value

Added value: +{
+  "description": "Value filter for the second cross-cutting dimension, e.g. AGEGROUP_DAYS0-27. Discover the position from returned dim2Type/dim2 pairs; metadata does not identify the slot. Empty strings are ignored with a notice.",
+  "type": "string"
+}

addedInput schema / properties / dim3_value

Added value: +{
+  "description": "Value filter for the third cross-cutting dimension, e.g. CHILDCAUSE_CH9. Discover the position from returned dim3Type/dim3 pairs; metadata does not identify the slot. Empty strings are ignored with a notice.",
+  "type": "string"
+}

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

changedInput schema / properties / region_codes / description

Previous value: -"WHO region codes to filter on, e.g. [\"AFR\",\"EUR\",\"AMR\",\"EMR\",\"SEAR\",\"WPR\"]. Returns the aggregate row for each named WHO region — not per-country rows within it. To get country-level data for a region, use who_list_dimension_values with dimension=\"COUNTRY\" and parent_code set to the region code to retrieve the ISO codes for countries in that region, then pass those to country_codes. Use who_list_dimension_values with dimension=\"REGION\" to see all valid region codes. Mutually exclusive with country_codes and income_group_codes."New value: +"WHO region codes to filter on, e.g. [\"AFR\",\"EUR\",\"AMR\",\"EMR\",\"SEAR\",\"WPR\"]. Returns the aggregate row for each named WHO region. To get country-level data for a region, use who_list_dimension_values with dimension=\"COUNTRY\" and parent_code set to the region code to retrieve WHO country codes, then pass those to country_codes. Use who_list_dimension_values with dimension=\"REGION\" to see all valid region codes. Mutually exclusive with country_codes and income_group_codes."

addedOutput schema / properties / appliedFilters / properties / dim2Value

Added value: +{
+  "description": "dim2_value filter applied, if any.",
+  "type": "string"
+}

addedOutput schema / properties / appliedFilters / properties / dim3Value

Added value: +{
+  "description": "dim3_value filter applied, if any.",
+  "type": "string"
+}

addedOutput schema / properties / rows / items / properties / dim3

Added value: +{
+  "description": "Third cross-cutting dimension value.",
+  "type": "string"
+}

addedOutput schema / properties / rows / items / properties / dim3Type

Added value: +{
+  "description": "Third cross-cutting dimension type, e.g. CHILDCAUSE.",
+  "type": "string"
+}

Changedwho_search_indicators3 fields changed

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."

6 tool updatesAug 25, 2026

Changedwho_get_indicator_metadata6 fields changed

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",
+      "notFound"
+    ]
+  },
+  {
+    "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: `all_not_found`: No requested indicator code resolved to a catalog entry. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "all_not_found"
+          ],
+          "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",
-  "notFound"
-]

Changedwho_list_dimension_values6 fields changed

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"
-]

Changedwho_list_dimensions6 fields changed

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": [
+      "dimensions"
+    ]
+  },
+  {
+    "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: -[
-  "dimensions"
-]
```

Changedwho_list_indicators6 fields changed

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"
-]

Changedwho_query_indicator_data6 fields changed

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": [
+      "rows",
+      "appliedFilters",
+      "totalRows",
+      "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: `indicator_not_found`: The indicator code returned HTTP 404 from the GHO API. `no_data`: The indicator exists but no data rows matched the applied filters. `ambiguous_spatial_filter`: More than one of country_codes, region_codes, or income_group_codes were provided. `invalid_year_range`: year_from is greater than year_to, so the time filter can match no rows. `invalid_query`: The GHO API rejected the generated OData query because a supplied filter value is not a valid literal. `malformed_identifier`: indicator_code 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": [
+            "indicator_not_found",
+            "no_data",
+            "ambiguous_spatial_filter",
+            "invalid_year_range",
+            "invalid_query",
+            "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: -[
-  "rows",
-  "appliedFilters",
-  "totalRows",
-  "totalCount",
-  "offset",
-  "hasMore",
-  "pageInfo"
-]

Changedwho_search_indicators6 fields changed

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"
-]

3 tool updatesAug 18, 2026

Changedwho_get_indicator_metadata4 fields changed

changedOutput schema / properties / indicators / description

Previous value: -"Metadata for each code that returned results."New value: +"Metadata for each code that resolved to a catalog entry."

changedOutput schema / properties / indicators / items / properties / dimensions / description

Previous value: -"Dimensions this indicator supports for filtering in who_query_indicator_data."New value: +"Dimensions this indicator supports for filtering in who_query_indicator_data. Empty when the GHO dimension table lists none for this code — see dimensionsNote."

addedOutput schema / properties / indicators / items / properties / dimensionsNote

Added value: +{
+  "description": "Present only when dimensions is empty: explains that the listing is missing upstream rather than the indicator being absent, and how to recover the dimensions from a sample data row.",
+  "type": "string"
+}

changedOutput schema / properties / notFound / description

Previous value: -"Indicator codes that returned no metadata — they may not exist in the GHO catalog."New value: +"Indicator codes that resolved to neither a catalog name nor any dimension rows — they do not exist in the GHO catalog."

Changedwho_list_dimension_values11 fields changed

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"
+]

Changedwho_query_indicator_data4 fields changed

changedInput schema / properties / region_codes / description

Previous value: -"WHO region codes to filter on, e.g. [\"AFR\",\"EUR\",\"AMR\",\"EMR\",\"SEAR\",\"WPR\"]. Returns the aggregate row for each named WHO region — not per-country rows within it. To get country-level data for a region, use who_list_dimension_values with dimension=\"COUNTRY\" and filter by parentCode to retrieve the ISO codes for countries in that region, then pass those to country_codes. Use who_list_dimension_values with dimension=\"REGION\" to see all valid region codes. Mutually exclusive with country_codes and income_group_codes."New value: +"WHO region codes to filter on, e.g. [\"AFR\",\"EUR\",\"AMR\",\"EMR\",\"SEAR\",\"WPR\"]. Returns the aggregate row for each named WHO region — not per-country rows within it. To get country-level data for a region, use who_list_dimension_values with dimension=\"COUNTRY\" and parent_code set to the region code to retrieve the ISO codes for countries in that region, then pass those to country_codes. Use who_list_dimension_values with dimension=\"REGION\" to see all valid region codes. Mutually exclusive with country_codes and income_group_codes."

addedOutput schema / properties / rows / items / properties / parentLocation

Added value: +{
+  "description": "Name of the WHO region this row sits under, e.g. \"Western Pacific\" for a JPN row. Not a label for spatialDim itself — the upstream row carries no name for its own spatial entity. Absent when spatialDim is already a region or income group.",
+  "type": "string"
+}

addedOutput schema / properties / rows / items / properties / parentLocationCode

Added value: +{
+  "description": "Code of the WHO region this row sits under, e.g. \"WPR\". Pass to region_codes to query that region's own aggregate rows. Absent alongside parentLocation.",
+  "type": "string"
+}

removedOutput schema / properties / rows / items / properties / spatialLabel

Removed value: -{
-  "description": "Human-readable spatial label, e.g. WHO region name for a country row.",
-  "type": "string"
-}

2 tool updatesAug 18, 2026

Changedwho_query_indicator_data10 fields changed

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based row offset for pagination. Default 0. Pages are stable because rows are returned in a deterministic order — read hasMore and nextOffset from the response to continue. An offset at or beyond totalRows returns an empty rows array, not an error.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / sort

Added value: +{
+  "default": "year_desc",
+  "description": "Row ordering: \"year_desc\" (default) returns the most recent years first, \"year_asc\" the earliest first. Ties are broken by spatial code, then dimension, then row id.",
+  "enum": [
+    "year_desc",
+    "year_asc"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / appliedFilters / properties / ordering

Added value: +{
+  "description": "Row ordering applied to the query, e.g. \"most recent first (year_desc)\".",
+  "type": "string"
+}

changedOutput schema / properties / appliedFilters / required

Previous value: -[
-  "indicatorCode"
-]New value: +[
+  "indicatorCode",
+  "ordering"
+]

addedOutput schema / properties / hasMore

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

changedOutput schema / properties / notice / description

Previous value: -"Present when the limit was reached and not all rows were returned. Explains how to retrieve additional rows."New value: +"Present when rows were withheld or the requested offset ran past the end of the result set. Explains how to reach the remaining rows."

addedOutput schema / properties / offset

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

addedOutput schema / properties / pageInfo

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

changedOutput schema / required

Previous value: -[
-  "rows",
-  "appliedFilters",
-  "totalRows",
-  "totalCount"
-]New value: +[
+  "rows",
+  "appliedFilters",
+  "totalRows",
+  "totalCount",
+  "offset",
+  "hasMore",
+  "pageInfo"
+]

Changedwho_search_indicators7 fields changed

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"
+]

1 tool updateJun 13, 2026

Changedwho_query_indicator_data3 fields changed

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Alias of totalRows for cross-tool consistency — total rows before the limit.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the result was capped at the requested limit.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "rows",
-  "appliedFilters",
-  "totalRows"
-]New value: +[
+  "rows",
+  "appliedFilters",
+  "totalRows",
+  "totalCount"
+]

1 tool updateJun 4, 2026

Changedwho_query_indicator_data2 fields changed

changedOutput schema / properties / rows / items / properties / year / description

Previous value: -"Year of the data point."New value: +"Year of the data point. Absent when the upstream row has no TimeDim (time-independent entries)."

changedOutput schema / properties / rows / items / required

Previous value: -[
-  "indicatorCode",
-  "year"
-]New value: +[
+  "indicatorCode"
+]

3 tool updatesMay 30, 2026

Changedwho_list_indicators4 fields changed

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"
+]

Changedwho_query_indicator_data5 fields changed

addedOutput schema / properties / appliedFilters

Added value: +{
+  "additionalProperties": false,
+  "description": "Filters that were applied to the query.",
+  "properties": {
+    "dim1Value": {
+      "description": "dim1_value filter applied, if any.",
+      "type": "string"
+    },
+    "indicatorCode": {
+      "description": "Indicator code that was queried.",
+      "type": "string"
+    },
+    "sex": {
+      "description": "Sex filter value applied, if any.",
+      "type": "string"
+    },
+    "spatialFilter": {
+      "description": "Active spatial filter summary, e.g. \"country_codes: JPN,USA\" or \"region_codes: EUR\".",
+      "type": "string"
+    },
+    "yearRange": {
+      "description": "Applied year range, e.g. \"2015–2023\". Absent when no year filter was set.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "indicatorCode"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Present when the limit was reached and not all rows were returned. Explains how to retrieve additional rows.",
+  "type": "string"
+}

removedOutput schema / properties / truncated

Removed value: -{
-  "description": "True when totalRows exceeds the limit and not all rows were returned.",
-  "type": "boolean"
-}

removedOutput schema / properties / truncatedNote

Removed value: -{
-  "description": "Present when truncated is true. Explains how to retrieve additional rows, e.g. by narrowing filters or increasing the limit.",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "rows",
-  "totalRows",
-  "truncated"
-]New value: +[
+  "rows",
+  "appliedFilters",
+  "totalRows"
+]

Changedwho_search_indicators6 fields changed

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"
+]

6 tool updatesMay 25, 2026
- First observedwho_get_indicator_metadata
- First observedwho_list_dimension_values
- First observedwho_list_dimensions
- First observedwho_list_indicators
- First observedwho_query_indicator_data
- First observedwho_search_indicators

Related MCP Connectors

Statistics of the WorldB
com.statisticsoftheworld
330+ indicators for 217 countries from the IMF, World Bank, WHO and national statistics offices.
Open Data Research & Data
172
https://statisticsoftheworld.com/api/mcp
Who GhoA
io.github.pipeworx-io
WHO GHO MCP — World Health Organization Global Health Observatory (free, no auth)
Open Data Research & Data
472
https://gateway.pipeworx.io/who-gho/mcp
DaedalMap UN Sustainable Development GoalsA
com.daedalmap
UN Sustainable Development Goal indicators for all 17 goals, curated by country and year. Free.
Government Data Open Data Research & Data
422
https://app.daedalmap.com/mcp/un_sdg
DaedalMap World Development IndicatorsA
com.daedalmap
World Bank World Development Indicators: curated country-year economy, health, education and more.
Open Data Research & Data Government Data
422
https://app.daedalmap.com/mcp/world_bank_wdi

Related MCP Servers

WHO MCP Server
Government Data Open Data Biology & Medicine
openpharma-org
A
license
B
quality
D
maintenance
Provides access to the World Health Organization's Global Health Observatory data, enabling AI assistants to search, retrieve, and analyze comprehensive health indicators, country statistics, disease burden data, and regional health trends through WHO's OData API.
Updated a year ago (2025-12-16 22:24 UTC)
1
MIT
@pipeworx/who-euro
Health & Wellness Open Data Government Data
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables querying WHO/Europe health statistics by searching indicators, retrieving time-series data by country and year, listing datasets and measures, and accessing metadata for 2,657 indicators across 22 datasets and 53 countries.
Updated a day ago (2026-11-06 20:51 UTC)
283 npm
MIT
who-gho
Government Data Biology & Medicine Open Data
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables querying World Health Organization Global Health Observatory data via natural language, free and without authentication.
Updated a day ago (2026-11-06 20:51 UTC)
249 npm
MIT
who-tb
Biology & Medicine Open Data
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables querying WHO Global Tuberculosis Programme data, including TB burden estimates, case notifications, and programme financing across 217 countries from 2000 onward.
Updated a day ago (2026-11-06 20:52 UTC)
295 npm
MIT

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.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources