Skip to main content
Glama

Who Gho List Countries

who_gho_list_countries
Read-onlyIdempotent

Return all WHO-recognized countries with their 3-letter ISO code, display name, and parent region code. Use the ISO codes returned here as the country parameter in get_data (e.g., "USA", "GBR", "JPN").

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of countries
countriesYesList of all countries with ISO codes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is fully covered. The description adds that the call is exhaustive ('all WHO-recognized countries') and what each entry carries, but says nothing about pagination, result size, or whether the list ever changes — the openWorld hint is left unexplained.

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, zero filler: the first defines the result set, the second states the downstream use. The most actionable information, the code format and where to plug it in, is placed where it is read.

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?

For a parameterless enumeration whose output schema already documents the return shape, the description supplies everything else an agent needs: what is returned, in what format, and the exact next call it enables. Nothing material to correct invocation 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?

The tool takes zero parameters, so the schema needs no explanation and the baseline is elevated. The description usefully spends its words instead on the ISO code format ('USA', 'GBR', 'JPN') that this tool's output must feed into downstream tools.

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 ('Return all WHO-recognized countries') with the exact payload ('3-letter ISO code, display name, and parent region code'), so the scope and output shape are unambiguous. It also implicitly separates itself from the data-retrieval sibling by being the enumeration step that feeds it.

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?

Explicitly tells the agent when to reach for it: to obtain ISO codes that then become the 'country' parameter in get_data, with example values. No when-not guidance or exclusions are given, but for a reference-list tool with no near-equivalent sibling that gap is minor.

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.