WHO MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| who-healthC | Unified tool for WHO Global Health Observatory operations: access health indicators, country statistics, and regional data via the modern OData API. Provides access to comprehensive health data from the World Health Organization covering topics like life expectancy, disease burden, health systems, and risk factors using standard OData query syntax. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'who-health' has a clearly defined purpose focused on WHO Global Health Observatory operations, making it impossible for an agent to misselect between non-existent alternatives.
A single tool inherently exhibits perfect naming consistency as there are no other tools to compare against. The name 'who-health' follows a clear and descriptive pattern that aligns with the server's purpose, with no deviations or mixed conventions present.
A single tool is generally too few for a server's purpose unless it is extremely narrow, but here the tool description suggests broad capabilities (access health indicators, country statistics, regional data, etc.). This likely represents a significant under-scoping, as typical data access servers benefit from multiple specialized tools for different query types or operations.
The tool claims to provide comprehensive access via OData queries, which could theoretically cover many operations, but having only one tool may create gaps in usability or functionality. For example, there are no dedicated tools for common actions like listing available datasets, filtering by specific criteria, or managing queries, which might hinder agent workflows despite the broad OData coverage.