Skip to main content
Glama

Who Gho Get Data

who_gho_get_data
Read-onlyIdempotent

Get World Health Organization health statistics for a country and year, life expectancy, immunization coverage, mortality, disease burden, risk factors and health system measures from the Global Health Observatory. Accepts a plain indicator name such as "measles immunization coverage" and a plain country name such as "Kenya"; both are resolved to WHO codes and the response says what it resolved to. If the requested year has no data it returns the latest year that does, and says which.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "2022",
      "country": "Kenya",
      "indicator": "measles immunization coverage"
    },
    "name": "who_gho_get_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear, e.g. "2020". If that year has no data the latest available year is returned instead, flagged as year_fallback.
countryNoCountry NAME ("Kenya", "United States") or ISO3 code ("KEN", "USA").
indicatorYesIndicator NAME ("measles immunization coverage", "life expectancy at birth") or a GHO code ("mslv", "WHOSIS_000001"). Names are resolved, do not invent a code.

Output Schema

NameRequiredDescriptionDefault
dataYesArray of data values (max 100 returned)
totalYesTotal number of data values found
returnedYesNumber of data values actually returned (max 100)
indicatorYesThe requested indicator code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / indicator / description
      Previous value: -"Indicator NAME (\"measles immunization coverage\", \"life expectancy at birth\") or a GHO code (\"mslv\", \"WHOSIS_000001\"). Names are resolved — do not invent a code."New value: +"Indicator NAME (\"measles immunization coverage\", \"life expectancy at birth\") or a GHO code (\"mslv\", \"WHOSIS_000001\"). Names are resolved, do not invent a code."
  2. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / year / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "string",
      +  "null",
      +  "number"
      +]
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, and the description adds real context on top: plain names are resolved to WHO codes, the response reports what it resolved to, and a missing year silently falls back to the latest available year with a flag. That fallback behavior is the kind of surprise an agent needs warned about. It stops short of noting rate limits or coverage gaps in the indicator catalog.

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, front-loaded with the resource and scope, then the two behavioral guarantees (name resolution and year fallback). No filler, though the middle sentence repeats the year-fallback point already made at the end and in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't specify return shape, and annotations carry the safety profile; the resolved-name and fallback disclosures fill the remaining behavioral gap for a 3-parameter read. It could be more complete by pointing to the sibling that lists available countries/indicators for discovery.

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 coverage is 100% and the schema already documents the year fallback flag, country name/ISO3 forms, and indicator name/GHO code forms, so the description largely restates it. It does add the useful framing that user-supplied names are accepted verbatim rather than requiring the caller to construct codes, but no new syntax or constraints beyond the schema.

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 ('Get World Health Organization health statistics ... from the Global Health Observatory') and scopes it to a country and year across enumerated domains (life expectancy, immunization, mortality, disease burden, risk factors, health system measures). This is clearly a data-retrieval tool, distinguishable from a country-listing sibling like who_gho_list_countries without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the reader infers 'call this when you want an indicator value for a country-year.' There is no explicit when-not guidance and no named alternative (e.g., the sibling that lists countries or resolves indicators), so the agent must reason about routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.