Medical Terminologies MCP

Search ICD-11

icd11_search

Read-onlyIdempotent

Search medical conditions by name or keyword to retrieve ICD-11 codes, official titles, and relevance scores. Supports WHO's official translations in multiple languages.

Instructions

Search for medical conditions, diseases, and health problems in ICD-11 (International Classification of Diseases, 11th Revision).

Use this tool to:

Find ICD-11 codes for diagnoses
Search for diseases by name or keyword
Look up conditions in multiple languages

Set language for WHO's official translations — e.g. language: "pt" searches and returns the official Portuguese (pt-BR) ICD-11 labels. Never machine-translated.

Returns matching entities with codes, titles, and relevance scores.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Search text (disease name, symptom, or keyword)
`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
`max_results`	No	Maximum number of results (1-100). Default: 25

Output Schema

TableJSON Schema

Name	Required	Description
`query`	Yes
`entities`	Yes
`provenance`	Yes	Provenance block (contract v1.0): source, URL, data vintage, extraction instant, citation, license
`attribution`	Yes	Canonical source URLs of this response (attribution list)
`total_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.9.1Sep 1, 2026
- removedOutput schema / properties / entities / items / properties / code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / entities / items / properties / code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / provenance / properties / data_vintage / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / provenance / properties / data_vintage / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / provenance / properties / license / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / provenance / properties / license / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed4 schema fields changedv1.8.0Aug 10, 2026

changedInput schema / properties / language / description

Previous value: -"Language code (default: en)"New value: +"Language code (default: en). Returns the source's OFFICIAL translation when it exists (e.g. 'pt' for official Portuguese); content is never machine-translated."

addedOutput schema / properties / attribution

Added value: +{
+  "description": "Canonical source URLs of this response (attribution list)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / provenance

Added value: +{
+  "additionalProperties": false,
+  "description": "Provenance block (contract v1.0): source, URL, data vintage, extraction instant, citation, license",
+  "properties": {
+    "citation": {
+      "description": "Ready-to-use citation/attribution string",
+      "type": "string"
+    },
+    "data_vintage": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Version/release of the data as exposed by the source; null when not exposed"
+    },
+    "license": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "License / legal regime of the data"
+    },
+    "retrieved_at": {
+      "description": "Real instant of the upstream extraction (ISO-8601, UTC). Responses served from cache keep the ORIGINAL fetch instant.",
+      "type": "string"
+    },
+    "source": {
+      "description": "Official upstream source of this data",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "Canonical URL of the source (API base or dataset release)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "source_url",
+    "data_vintage",
+    "retrieved_at",
+    "citation",
+    "license"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "query",
-  "total_count",
-  "entities"
-]New value: +[
+  "query",
+  "total_count",
+  "entities",
+  "provenance",
+  "attribution"
+]

Changed5 schema fields changedv1.5.7Jun 21, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / entities / items / properties / code / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / entities / items / properties / code / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / total_count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total_count / minimum
```
Added value: +-9007199254740991
```
First observedv1.2.1May 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It adds meaningful behavioral context by emphasizing that language selection uses WHO's official translations and is never machine-translated, and it discloses that results include codes, titles, and relevance scores.

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?

The description is front-loaded with a clear first sentence, followed by a concise bullet list of use cases and a focused note on language behavior. It is appropriately sized with minimal redundancy, though the second bullet repeats some of the first sentence's content.

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?

Given the output schema and 100% schema coverage, the description provides enough context for invoking the tool correctly: it explains search intent, language behavior, and result contents. It does not fully address how this tool relates to similar ICD-11 siblings like icd11_hierarchy or icd11_lookup, which is a minor completeness gap for selection.

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?

Input schema coverage is 100%, so parameters are already documented in detail. The description adds a helpful example for the language parameter ('pt' returns official Portuguese labels) and reinforces the official-translation guarantee, but it does not meaningfully extend the schema's existing parameter explanations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it searches for medical conditions, diseases, and health problems in ICD-11. It also lists concrete use cases such as finding ICD-11 codes and searching by keyword. It does not explicitly contrast itself with sibling tools like icd11_lookup, so it is clear but not fully differentiated.

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 provides clear context for when to use the tool: 'Use this tool to find ICD-11 codes for diagnoses, search for diseases by name or keyword, and look up conditions in multiple languages.' It gives practical guidance on language selection with an example, but it does not mention exclusions or when to prefer an alternative such as icd11_lookup.

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