Skip to main content
Glama

WHO Global Health Observatory values for one country

health_who_global_health_stats
Read-only

WHO Global Health Observatory values for one country and one indicator (OData API): indicator name, year, sex or group breakdown, value with uncertainty interval. Up to 20 rows, newest year first. Default indicator is life expectancy at birth. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "country": "<country>"
    },
    "name": "health_who_global_health_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many rows, 1 to 20 (default 5)
countryYesISO 3166-1 alpha-3 country code, e.g. TUR
indicatorNoWHO indicator code, letters, digits and underscores (default WHOSIS_000001)

Output Schema

NameRequiredDescriptionDefault
sourceNo
valuesNo
countryNo
checkedAtNo
indicatorNo
indicatorNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the supplied annotations, which declare read-only and open-world, the description discloses the paid-call model: $0.002 per successful call, x402 payment in USDC across multiple chains, and no charge on failure. It also discloses the result-size cap and the sort order, which materially shape how an agent plans and budgets the call.

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?

It is a single dense paragraph that front-loads the resource and scope, then returns, limits, defaults, and price. Every sentence carries facts the agent needs, and there is no 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?

The tool has three parameters with full schema coverage, an output schema, and annotations covering safety. The description adds the operational facts the structured data lacks: cost model, row ceiling, sort order, and default indicator. Nothing an agent needs in order to call it correctly 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 description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by naming the default indicator (life expectancy at birth) and by tying the row cap to newest-first ordering. The only gap is that 'sex or group breakdown' is never described as selectable, so the agent could wonder whether it is a parameter.

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 title and description state the specific verb and resource: retrieve WHO Global Health Observatory values for one country and one indicator, and they enumerate the returned fields (indicator name, year, sex/group breakdown, value with uncertainty interval). The scope is narrow and explicit, which cleanly separates it from the other health data sources in the sibling set.

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?

The description gives usable context (one country, one indicator, maximum 20 rows, newest year first, default indicator is life expectancy), so the agent can infer when the tool fits. However, it never states when not to use it or which sibling to use instead, for example for multi-country comparisons or mortality series from another source.

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.

Resources