Medical Terminologies MCP

Capítulo da CID-10

cid10_chapter

Read-onlyIdempotent

Retrieve a CID-10 chapter (1-22) with all its constituent groups, including titles and code ranges, to build hierarchical browsers or locate the group for a code.

Instructions

Get one CID-10 chapter and its constituent groups (e.g., "Chapter IX → I00-I02 Febre reumática aguda, I05-I09 Doenças reumáticas crônicas do coração, ...").

Use this tool to:

Drill from a chapter into its groups (code ranges with Portuguese titles)
Build hierarchical browsers
Find which group contains a code range

Provide the chapter number num as an integer 1-22 (chapter I = 1, IX = 9). Numbers outside 1-22 are rejected with a validation error. Returns the chapter (title and code range) plus ALL its groups in one response — no pagination; the 22 chapters hold 275 groups in total. Answered locally from the bundled CID-10 V2008; no network call.

Which CID-10 tool: use cid10_chapters first if you do not know the chapter number (it lists all 22 with code ranges); use cid10_lookup for one specific code and cid10_search to find codes by Portuguese text. For the international ICD-11, use icd11_chapters.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`num`	Yes	Chapter number (1-22). CID-10 V2008 has 22 chapters.

Output Schema

TableJSON Schema

Name	Required	Description
`num`	Yes
`found`	Yes
`groups`	Yes
`chapter`	Yes
`provenance`	Yes	Provenance block (contract v1.1): 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.

Changed3 schema fields changedv1.15.0Sep 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"
+]

Changed1 schema field changedv1.11.0Sep 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed4 schema fields changedv1.9.1Sep 1, 2026
- 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"
+]
```

Changed3 schema fields changedv1.8.0Aug 10, 2026

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: -[
-  "num",
-  "found",
-  "chapter",
-  "groups"
-]New value: +[
+  "num",
+  "found",
+  "chapter",
+  "groups",
+  "provenance",
+  "attribution"
+]

Changed4 schema fields changedv1.5.7Jun 21, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / chapter / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "code_end": {
-        "type": "string"
-      },
-      "code_start": {
-        "type": "string"
-      },
-      "num": {
-        "type": "integer"
-      },
-      "title": {
-        "type": "string"
-      },
-      "title_short": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "num",
-      "code_start",
-      "code_end",
-      "title",
-      "title_short"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "code_end": {
+        "type": "string"
+      },
+      "code_start": {
+        "type": "string"
+      },
+      "num": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "title": {
+        "type": "string"
+      },
+      "title_short": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "num",
+      "code_start",
+      "code_end",
+      "title",
+      "title_short"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / num / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / num / minimum
```
Added value: +-9007199254740991
```

First observedv1.2.1May 11, 2026

TDQS

A4.2/5.0

Behavior2/5

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

Annotations already cover the safety profile (readOnly/idempotent/non-destructive), and the description usefully adds that all groups return in one response with no pagination and that the 275 groups come from a bundled local dataset. However, 'Answered locally from the bundled CID-10 V2008; no network call' directly conflicts with the openWorldHint=true annotation, which asserts interaction with an open world of external entities — the description describes a closed, offline data source.

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-loaded with the purpose and scope, then organized into use-case bullets and a routing paragraph. Slightly verbose (the embedded Portuguese example runs long), but every section carries information and nothing is padded.

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 single-parameter lookup with an output schema present (so return values need no explanation), the description still covers scope, all 22 chapters/275 groups volume, no-pagination behavior, data source, error behavior, and sibling routing. Nothing an agent needs 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 coverage is 100% (baseline 3), and the description still adds real meaning beyond the schema: the Roman-numeral mapping (chapter I = 1, IX = 9) and the rejection behavior for numbers outside 1-22. These go beyond the bare 'integer 1-22' in the schema.

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+resource ('Get one CID-10 chapter and its constituent groups') and concretely distinguishes itself from siblings by naming cid10_chapters, cid10_lookup, cid10_search and icd11_chapters with the conditions that select each. An agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use bullets (drill from chapter into groups, build hierarchical browsers, find which group contains a range) plus explicit alternatives: use cid10_chapters when the chapter number is unknown, cid10_lookup for a single code, cid10_search for Portuguese text, icd11_chapters for ICD-11. When/when-not and alternatives are all present.

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