Skip to main content
Glama
Sign In
whiteknightonhorse

APIbase

by whiteknightonhorse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

WHO Member Countries

who.health.countries
Read-onlyIdempotent

Retrieve a list of all 194 WHO member countries and territories with codes and names. Use the codes to filter health indicators in who.data queries.

Instructions

List all 194 WHO member countries and territories with codes and names. Use returned country codes with who.data to filter health indicators by country.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of countries to return, max 200 (default 50)
searchNoPartial country name to filter (e.g. "United", "Germany", "Brazil")

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0
  2. Removedv1.0.20
  3. Addedv1.0.16

TDQS

A4.3/5.0
Behavior4/5

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

Annotations (readOnlyHint, idempotentHint, etc.) already indicate a safe read operation. The description adds context about the exact output (194 countries, codes, names) and a practical use case, which is valuable 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?

Two sentences efficiently convey the tool's purpose, content, and usage hint. No unnecessary words; front-loaded with the main action.

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 presence of an output schema and the simple nature of the tool, the description covers all necessary context: what it returns, how to use it with sibling tools, and the default scope.

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% with clear parameter descriptions. The description does not add new semantic information beyond what is already in the schema, though it does reinforce the purpose of the parameters implicitly.

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 clearly states the tool lists WHO member countries and territories with codes and names, and provides a specific use case (using codes with who.data). It distinguishes from sibling tools by specifying the resource and linking to related tools.

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?

The description explicitly recommends using returned country codes with 'who.data' to filter health indicators. While it does not directly exclude alternative uses, the context provided is clear and offers practical guidance for integration.

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

Deploy Server

Other Tools