Medical Terminologies MCP

Terminology Versions

terminology_versions

Read-onlyIdempotent

List release versions, dates, publishers, source URLs, and update cadence for queried medical terminologies, or filter to one, to verify before batch runs and cite data versions.

Instructions

List the current version, release date, publisher, source URL, and update cadence of every terminology this server queries against.

Useful for pipeline maintainers who need to:

Confirm which release of ICD-11 / LOINC / RxNorm / MeSH / ATC the server is querying before a batch run.
Verify the bundled CID-10 (frozen at V2008) and ICD-10 → ICD-11 transition tables (currently 2025-01) match expectations.
Cite the data version in research artifacts.

Pass terminology to filter to a single entry; otherwise the full set of 7 is returned. The ICD-10 → ICD-11 version reads live from the bundled dataset; everything else is metadata maintained alongside the project release.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`terminology`	No	Filter to a single terminology. Omit to return all 7.

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes
`generated`	Yes	Date this snapshot was generated.
`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)
`terminologies`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.0Oct 4, 2026

changedInput schema / properties / terminology / description

Previous value: -"Filter to a single terminology. Omit to return all 8."New value: +"Filter to a single terminology. Omit to return all 7."

changedInput schema / properties / terminology / enum

Previous value: -[
-  "icd11",
-  "icd10",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh",
-  "atc",
-  "cid10"
-]New value: +[
+  "icd11",
+  "icd10",
+  "loinc",
+  "rxnorm",
+  "mesh",
+  "atc",
+  "cid10"
+]

changedOutput schema / properties / terminologies / items / properties / code / enum

Previous value: -[
-  "icd11",
-  "icd10",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh",
-  "atc",
-  "cid10"
-]New value: +[
+  "icd11",
+  "icd10",
+  "loinc",
+  "rxnorm",
+  "mesh",
+  "atc",
+  "cid10"
+]

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
```
Changed8 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"
+]
```
- removedOutput schema / properties / terminologies / items / properties / changelog_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / terminologies / items / properties / changelog_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / terminologies / items / properties / notes / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / terminologies / items / properties / notes / 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: -[
-  "generated",
-  "total",
-  "terminologies"
-]New value: +[
+  "generated",
+  "total",
+  "terminologies",
+  "provenance",
+  "attribution"
+]

Changed7 schema fields changedv1.5.7Jun 21, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / terminologies / items / properties / changelog_url / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / terminologies / items / properties / changelog_url / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / terminologies / items / properties / notes / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / terminologies / items / properties / notes / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / total / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total / minimum
```
Added value: +-9007199254740991
```
Addedv1.4.0May 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds provenance detail: the full set of 7 is returned by default, the ICD-10 → ICD-11 version reads live from the bundled dataset while everything else is release-maintained metadata. This live-vs-static distinction is useful behavioral context 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the returned fields, then a scannable bullet list of use cases, then the parameter behavior. The bullets are slightly verbose but each carries real information; nothing is wasted.

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?

An output schema exists, so return values need not be explained, yet the description even enumerates the returned fields. It covers filtering, default behavior, data provenance, and the one-parameter surface, leaving no gap for correct invocation.

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% and the enum already documents the filter values and the omit-to-return-all behavior. The description restates the same filtering semantics, adding little meaning beyond the schema, so the baseline 3 is appropriate.

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 (List) and resource (version, release date, publisher, source URL, update cadence of every terminology) with a clear scope. This is instantly distinguishable from every sibling, which are all code-lookup/search tools, so an agent can tell it apart without opening a schema.

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?

Provides concrete when-to-use scenarios (confirm release before a batch run, verify bundled tables, cite data version in research). It gives clear positive guidance but does not explicitly name alternatives or exclusions, though the meta purpose has no meaningful sibling overlap.

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