Medical Terminologies MCP

Browse ICD-11 Hierarchy

icd11_hierarchy

Read-onlyIdempotent

Navigate the ICD-11 hierarchy to find parent or child entities.

Use this tool to:

Find broader categories (parents) of a condition
Find specific subtypes (children) of a condition
Understand the classification structure

Name the entity by code (a leaf code like "5A11", or a block range like "5A10-5A2Y" — blocks come back from 'parents' with an empty code and a code_range) or by uri (the URI any previous answer returned). Direction 'parents' returns ancestor categories, 'children' returns subcategories. ICD-10 codes (like "E11") are not ICD-11 codes: convert them first with map_icd10_to_icd11.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uri`	No	Entity URI as returned by icd11_lookup, icd11_search or a previous icd11_hierarchy call
`code`	No	ICD-11 code (e.g., "BA00", "5A11") or block range (e.g., "5A10-5A2Y")
`language`	No	Language code (default: en). Returns the source's OFFICIAL translation when it exists (e.g. 'pt' for official Portuguese); content is never machine-translated.	en
`direction`	Yes	Direction: "parents" for ancestors, "children" for subtypes

Output Schema

TableJSON Schema

Name	Required	Description
`code`	Yes
`entities`	Yes
`direction`	Yes
`provenance`	Yes	Provenance block: source, URL, data vintage, extraction instant, origin diagnostics, citation, license
`attribution`	Yes	Canonical source URLs of this response (attribution list)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / properties / provenance / properties / notices / description

Previous value: -"Notices the source publishes alongside the data (license statements, caveats), verbatim. Absent when there is none"New value: +"Caveats the source publishes about the data, verbatim (license statements are not repeated here; see the info://licenses resource). Absent when there is none"

Changed7 schema fields changedOct 8, 2026

changedOutput schema / properties / provenance / description

Previous value: -"Provenance block (contract v1.1): source, URL, data vintage, extraction instant, origin diagnostics, citation, license"New value: +"Provenance block: source, URL, data vintage, extraction instant, origin diagnostics, citation, license"

addedOutput schema / properties / provenance / properties / derivation_note

Added value: +{
+  "description": "What this server computed; present together with derived",
+  "type": "string"
+}

addedOutput schema / properties / provenance / properties / derived

Added value: +{
+  "description": "Present (true) only when this server computed the value (e.g. a ranking or summary statistics) instead of passing on what the source returned",
+  "type": "boolean"
+}

changedOutput schema / properties / provenance / properties / field_sources / description

Previous value: -"Present only when the response joins parts from different origins or extraction instants (contract v1.2): for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses"New value: +"Present only when the response joins parts from different origins or extraction instants: for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses"

addedOutput schema / properties / provenance / properties / notices

Added value: +{
+  "description": "Notices the source publishes alongside the data (license statements, caveats), verbatim. Absent when there is none",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

changedOutput schema / properties / provenance / properties / retrieval / description

Previous value: -"Origin diagnostics of THIS source in this call (contract v1.1): requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"New value: +"Origin diagnostics of THIS source in this call: requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"

addedOutput schema / properties / provenance / properties / revision

Added value: +{
+  "additionalProperties": false,
+  "description": "Whether the data can still change at the source: current = the version in force, the source may revise it; provisional = preliminary; final = will not change. Absent when unknown",
+  "properties": {
+    "note": {
+      "description": "O específico da fonte: o que revisa, quando, por quê",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "current = versão vigente, a fonte pode revisá-la; provisional = preliminar, incompleta ou sujeita a mudança (não compare como se fosse fechada); final = não muda mais, declarado pela fonte",
+      "enum": [
+        "current",
+        "provisional",
+        "final"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / provenance / properties / field_sources

Added value: +{
+  "description": "Present only when the response joins parts from different origins or extraction instants (contract v1.2): for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses",
+  "items": {
+    "additionalProperties": false,
+    "description": "Proveniência de um grupo de campos da resposta: de onde veio e quando foi extraído",
+    "properties": {
+      "data_vintage": {
+        "description": "Vintage/competência da sub-fonte",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "dataset_id": {
+        "description": "Identificador do conjunto da sub-fonte",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fields": {
+        "description": "Campos do payload atribuídos a esta sub-fonte",
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "retrieved_at": {
+        "description": "ISO-8601 da extração desta sub-fonte na origem",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "served_from_cache": {
+        "description": "true se esta sub-fonte veio do cache do servidor (retrieved_at é o da extração original); false se foi buscada nesta chamada; null se o servidor não distingue",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "source_url": {
+        "description": "URL canônica da sub-fonte que originou estes campos",
+        "type": "string"
+      }
+    },
+    "required": [
+      "fields",
+      "source_url",
+      "dataset_id",
+      "data_vintage",
+      "retrieved_at"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}

Changed3 schema fields changedSep 27, 2026

changedOutput schema / properties / provenance / description

Previous value: -"Provenance block (contract v1.0): source, URL, data vintage, extraction instant, citation, license"New value: +"Provenance block (contract v1.1): source, URL, data vintage, extraction instant, origin diagnostics, citation, license"

addedOutput schema / properties / provenance / properties / retrieval

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "anomalies": {
+          "description": "Anomalias superadas até o sucesso, somadas por classe, em ordem fixa; [] se nenhuma",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "count": {
+                "description": "Ocorrências desta classe na chamada",
+                "maximum": 9007199254740991,
+                "minimum": 1,
+                "type": "integer"
+              },
+              "kind": {
+                "description": "Classe da anomalia (vocabulário fechado do contrato)",
+                "enum": [
+                  "timeout",
+                  "network",
+                  "http_4xx",
+                  "http_5xx",
+                  "rate_limited",
+                  "malformed_body"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "count"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attempts": {
+          "description": "Tentativas somadas, incluindo as repetidas (>= requests)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "requests": {
+          "description": "Idas distintas à origem que compõem esta resposta (fatias, páginas)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "unstable": {
+          "description": "true se houve repetição (attempts > requests) ou alguma anomalia",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requests",
+        "attempts",
+        "anomalies",
+        "unstable"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Origin diagnostics of THIS source in this call (contract v1.1): requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"
+}

changedOutput schema / properties / provenance / required

Previous value: -[
-  "source",
-  "source_url",
-  "data_vintage",
-  "retrieved_at",
-  "citation",
-  "license"
-]New value: +[
+  "source",
+  "source_url",
+  "data_vintage",
+  "retrieved_at",
+  "retrieval",
+  "citation",
+  "license"
+]

Changed4 schema fields changedSep 13, 2026

changedInput schema / properties / code / description

Previous value: -"ICD-11 code to get hierarchy for"New value: +"ICD-11 code (e.g., \"BA00\", \"5A11\") or block range (e.g., \"5A10-5A2Y\")"

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "description": "Language code (default: en). Returns the source's OFFICIAL translation when it exists (e.g. 'pt' for official Portuguese); content is never machine-translated.",
+  "enum": [
+    "en",
+    "es",
+    "pt",
+    "fr",
+    "de",
+    "it",
+    "zh",
+    "ja",
+    "ar",
+    "ru"
+  ],
+  "type": "string"
+}

addedInput schema / properties / uri

Added value: +{
+  "description": "Entity URI as returned by icd11_lookup, icd11_search or a previous icd11_hierarchy call",
+  "format": "uri",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "code",
-  "direction"
-]New value: +[
+  "direction"
+]

Changed1 schema field changedSep 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the description wasn't obligated to cover safety. It adds genuine behavioral context anyway: that 'parents' can return block nodes with an empty code plus a code_range, and that language selection returns only official translations and never machine-translated content.

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?

Front-loads the core action, then uses a short bullet list for use cases and a compact paragraph for argument semantics. Slight redundancy remains, since direction and the code/uri roles are re-explained relative to the schema, but nothing is padding.

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?

With an output schema present, return values need no explanation. The description covers argument sourcing, direction semantics, language behavior, and the ICD-10 pitfall, so an agent has everything needed to call this tool correctly on the first attempt.

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 real meaning beyond the schema: the code argument accepts either a leaf code or a block range, and blocks surfaced by 'parents' arrive with an empty code and a code_range, which tells the agent how to feed results back in.

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 (navigate/browse) plus resource (ICD-11 hierarchy) and immediately scopes the two modes (parents vs children) so the agent can distinguish it from icd11_lookup and icd11_search. The example codes and block-range mention make the operation concrete rather than abstract.

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 'Use this tool to' bullets give clear when-to-use cases (find parents, find children, understand structure), and it explicitly routes ICD-10 input to map_icd10_to_icd11 and points at icd11_lookup/icd11_search for obtaining a URI. It stops short of an explicit when-not-to-use statement against the other icd11_* siblings, so it is strong but not fully exhaustive.

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

All Medical Terminologies MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.