DRGSystem — German medical coding catalogs

Regeln zu einem Kode (mit Stichtag)

rules_for_code

Read-onlyIdempotent

Liefert alle Regeln außerhalb des Katalogs, die einen ICD-, OPS- oder DRG-Kode betreffen: Deutsche Kodierrichtlinien, Entscheidungen des Schlichtungsausschusses Bund (§ 19 KHG) und SEG-4-Kodierempfehlungen des Medizinischen Dienstes — die verbindlichste zuerst, jeweils mit Datum, Geltungszeitraum und Link zur Quelle. Regeln am übergeordneten Kode gelten mit (8-98f → 8-98f.20). Mit 'aufnahmedatum' sagt 'anwendbarkeit' je Regel, ob sie für diesen Fall gilt, erst für spätere Aufnahmen oder nur bei einer am Stichtag laufenden MD-Prüfung.

Input Schema

Name	Required	Description
`code`	Yes	Kode in amtlicher Schreibweise oder normalisiert: ICD 'E43', 'E44.0'; OPS '8-98f.20', '898f20'; DRG 'F36A'.
`year`	No	Katalogjahr (z. B. 2026), nur ohne 'aufnahmedatum': liefert nur Regeln, die in diesem Jahrgang gelten.
`katalog`	No	Katalog des Kodes: 'ICD', 'OPS' oder 'DRG'. Leer lassen, dann wird er aus der Form des Kodes erkannt.
`pruefungAm`	No	Nur mit 'aufnahmedatum': Tag (yyyy-MM-dd), an dem die Rechnung in einer MD-Prüfung nach § 275 Abs. 1 Nr. 1 SGB V war. Manche Schlichtungsentscheidungen gelten auch für solche Rechnungen.
`aufnahmedatum`	No	Aufnahmedatum des Falls (yyyy-MM-dd). Leer lassen für alle Regeln ohne Fallbezug.

Output Schema

Name	Required	Description
`jahr`	No	Katalogjahr, auf das die Ereignisse gefiltert sind. Null: alle Jahrgänge.
`kode`	No	Der abgefragte Kode, normalisiert.
`items`	No	Die Ereignisse, das verbindlichste zuerst, innerhalb gleicher Verbindlichkeit das jüngste zuerst.
`gesamt`	No	Anzahl aller Ereignisse in 'items'.
`katalog`	No	Katalog des abgefragten Kodes.
`aufnahme`	No	Nur bei 'rules_for_case': Aufnahmedatum des Falls (yyyy-MM-dd).
`strittig`	No	Anzahl der Ereignisse mit Dissens (z. B. FoKA widerspricht der SEG-4-Empfehlung) — offene Streitfragen.
`pruefungAm`	No	Nur bei 'rules_for_case': Datum, an dem die Rechnung in MD-Prüfung war (yyyy-MM-dd).
`verbindlich`	No	Anzahl der Ereignisse, die für alle verbindlich sind (amtlich, Kodierrichtlinie, Schlichtung).
`zuletztVeroeffentlicht`	No	Datum des jüngsten Ereignisses (yyyy-MM-dd).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

changedOutput schema / properties / items / items / properties / quelle / enum

Previous value: -[
-  "Dkr",
-  "Schlichtung",
-  "Klarstellung",
-  "BfarmFaq",
-  "Seg4",
-  "MdRichtlinie",
-  "Bsg",
-  "Lsg",
-  "Foka",
-  "Verband"
-]New value: +[
+  "Dkr",
+  "DkrPsych",
+  "Schlichtung",
+  "Klarstellung",
+  "BfarmFaq",
+  "Seg4",
+  "MdRichtlinie",
+  "Bsg",
+  "Lsg",
+  "Foka",
+  "Verband"
+]

changedOutput schema / properties / katalog / enum

Previous value: -[
-  "ATC",
-  "DRG",
-  "DKR",
-  "ICD",
-  "IcdStats",
-  "Orphanet",
-  "OPS",
-  "OpsStats",
-  "PEPP",
-  "ZE",
-  "KH",
-  "IcdAlpha",
-  "SEG4KDE",
-  "OpsAlpha",
-  "LG",
-  "BFW",
-  "ZP",
-  "ET",
-  "HybridDRG"
-]New value: +[
+  "ATC",
+  "DRG",
+  "DKR",
+  "ICD",
+  "IcdStats",
+  "Orphanet",
+  "OPS",
+  "OpsStats",
+  "PEPP",
+  "ZE",
+  "KH",
+  "IcdAlpha",
+  "SEG4KDE",
+  "OpsAlpha",
+  "LG",
+  "BFW",
+  "ZP",
+  "ET",
+  "HybridDRG",
+  "DkrPsych"
+]

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / katalog / enum

Previous value: -[
-  "ATC",
-  "DRG",
-  "DKR",
-  "ICD",
-  "IcdStats",
-  "Orphanet",
-  "OPS",
-  "OpsStats",
-  "PEPP",
-  "ZE",
-  "KH",
-  "IcdAlpha",
-  "SEG4KDE",
-  "OpsAlpha",
-  "LG",
-  "BFW",
-  "ZP",
-  "ET"
-]New value: +[
+  "ATC",
+  "DRG",
+  "DKR",
+  "ICD",
+  "IcdStats",
+  "Orphanet",
+  "OPS",
+  "OpsStats",
+  "PEPP",
+  "ZE",
+  "KH",
+  "IcdAlpha",
+  "SEG4KDE",
+  "OpsAlpha",
+  "LG",
+  "BFW",
+  "ZP",
+  "ET",
+  "HybridDRG"
+]

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / katalog / enum

Previous value: -[
-  "ATC",
-  "DRG",
-  "DKR",
-  "ICD",
-  "IcdStats",
-  "Orphanet",
-  "OPS",
-  "OpsStats",
-  "PEPP",
-  "ZE",
-  "KH",
-  "IcdAlpha",
-  "SEG4KDE",
-  "OpsAlpha",
-  "LG",
-  "BFW"
-]New value: +[
+  "ATC",
+  "DRG",
+  "DKR",
+  "ICD",
+  "IcdStats",
+  "Orphanet",
+  "OPS",
+  "OpsStats",
+  "PEPP",
+  "ZE",
+  "KH",
+  "IcdAlpha",
+  "SEG4KDE",
+  "OpsAlpha",
+  "LG",
+  "BFW",
+  "ZP",
+  "ET"
+]

AddedSep 28, 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/closed-world, and the description adds real behavior: results are ordered most-binding-first, carry date, validity period and source link, and parent-code rules are inherited (8-98f → 8-98f.20). This goes well 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-loads what is returned, then explains inheritance and the applicability switch. Dense but every clause (source enumeration, sort order, inheritance example, applicability logic) carries information; parenthetical examples aid rather than pad.

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, full annotations, and 100% schema coverage, the description supplies the remaining semantics an agent needs — inheritance, ordering, and the conditional applicability model — so nothing required 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%, so baseline is 3, but the description adds cross-parameter semantics the schema doesn't: inheritance of parent-code rules and the conditional interaction of 'aufnahmedatum'/'pruefungAm'/'year' on applicability. It clarifies meaning beyond the per-param descriptions.

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 (Liefert) and resource (alle Regeln außerhalb des Katalogs zu ICD/OPS/DRG-Kodes) and enumerates the three source types (DKR, Schlichtungsausschuss, SEG-4). It is clearly distinguished from the catalog-rule sibling rules_get, which the description implicitly contrasts by saying 'außerhalb des Katalogs'.

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?

Gives explicit conditional usage: 'year' only without 'aufnahmedatum', 'pruefungAm' only with 'aufnahmedatum', and explains that 'aufnahmedatum' toggles per-rule 'anwendbarkeit'. It doesn't explicitly name sibling alternatives like rules_get, but the parameter-combination guidance is strong.

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

All DRGSystem — German medical coding catalogs 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.

Resources

Need Help?