Skip to main content
Glama

who-gho-mcp-server

by io.github.cyanheads

List GHO Dimension Values

who_list_dimension_values
Read-onlyIdempotent

List valid codes and labels for a WHO GHO dimension type such as COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, or AGEGROUP. Use this to discover valid filter values before calling who_query_indicator_data, or to confirm the correct ISO code for a country. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of values to return per page. Default 100, max 500.
offsetNoZero-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.
dimensionYesDimension type code. Use who_list_dimensions to discover all available codes. Common values: COUNTRY, REGION, SEX, WORLDBANKINCOMEGROUP, AGEGROUP.
parent_codeNoRestrict 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoPresent when values were withheld, the parent_code filter matched nothing, or the requested offset ran past the end. Explains what to do next.
offsetNoZero-based offset this page started at.
valuesNoValid values for this dimension type, for the requested page.
hasMoreNoTrue when more values remain beyond this page. Pair with nextOffset to continue.
pageInfoNoHuman-readable page position, e.g. "offset 0, showing 100 of 234". Use to construct the next offset.
dimensionNoThe requested dimension type code.
nextOffsetNoOffset to request for the next page. Absent when this page reached the end of the values.
totalCountNoTotal values for this dimension and filter, before the limit is applied.

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds valuable behavior beyond them: it notes paging is deterministic, explains that hierarchical dimensions use parent_code, and clarifies that offsets beyond totalCount return an empty array rather than an error. This gives the agent confidence in edge-case behavior.

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?

The description is two sentences, front-loading the core purpose and target dimensions, then immediately providing paging guidance. Every sentence earns its place with no fluff or repetition.

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?

Given the tool's moderate complexity (4 params, one optional filter), the description covers discovery, paging, and edge cases (empty arrays). Since an output schema exists, the description is not required to explain return values, and it doesn't need to—the offset parameter in the schema already mentions hasMore and nextOffset. All essential guidance 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% with each parameter described, so the baseline is 3. The description enriches this by giving a concrete example of using dimension='COUNTRY' with parent_code='EUR', which clarifies how parent_code works for hierarchical dimensions. This adds meaning beyond the schema's individual descriptions.

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 names a specific verb ('List') and a specific resource ('valid codes and labels for a WHO GHO dimension type'), and explicitly lists example dimension types (COUNTRY, REGION, etc.). It distinguishes itself from siblings by stating it is used to discover filter values before calling who_query_indicator_data and to confirm ISO codes, which differentiates it from who_list_dimensions (which lists dimension type codes).

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?

It clearly states when to use the tool: 'Use this to discover valid filter values before calling who_query_indicator_data, or to confirm the correct ISO code for a country.' It also refers the user to who_list_dimensions for discovering dimension type codes, providing an alternative. It does not explicitly state when not to use it, but the guidance is clear and contextual.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: browsing/searching indicators, fetching metadata, listing dimensions, listing dimension values, and querying data. There is minor overlap between listing and searching indicators, but the descriptions explicitly differentiate them (browse vs. keyword search), leaving no ambiguity.

Naming Consistency5/5

All tools follow the 'who_<verb>_<noun>' pattern (e.g., who_list_dimensions, who_query_indicator_data), with verbs like get, list, search, and query used consistently. The uniform prefix and structure create a predictable and coherent naming scheme.

Tool Count5/5

Six tools is an ideal size for this domain, covering the full WHO GHO workflow without redundancy. Each tool supports a distinct step in discovery and data retrieval, making the set well-scoped and efficient.

Completeness5/5

The tool set covers the entire necessary surface for working with WHO GHO data: discovering indicators (search/list), retrieving metadata, exploring dimensions and their values, and querying actual data with filters. No obvious gaps exist for a read-only health statistics API.

Resources