DRGSystem — German medical coding catalogs

Zusatzentgelte PEPP durchsuchen

zp_search

Read-onlyIdempotent

Durchsucht die Zusatzentgelte des PEPP-Entgeltkatalogs (Psychiatrie und Psychosomatik, ZP) nach Kode oder Leistungsbeschreibung. Die Treffer stehen in 'items' mit Betrag bzw. Spanne der Beträge, Herkunft (bewertet oder krankenhausindividuell) und der Anzahl der auslösenden OPS-Kodes. Für Zusatzentgelte im DRG-System ist ze_search zuständig.

Input Schema

Name	Required	Description
`year`	No	Katalogjahr (z. B. 2027). Leer lassen für das aktuellste verfügbare Jahr.
`limit`	No	Maximale Anzahl Treffer, 1 bis 100. Standard 25.
`query`	Yes	Suchbegriff: ZP-Kode (z. B. 'ZP04', 'ZP04.02', 'ZP2027-03') oder Leistungsbeschreibung (z. B. 'Gabe von Prothrombinkomplex').

Output Schema

Name	Required	Description
`info`	No	Was über den Jahrgang zu wissen ist, etwa «Version 2026» (ICD-10-GM 2027) oder «Vorabfassung». Null ohne.
`year`	No	Katalogjahr, aus dem alle Daten dieser Antwort stammen.
`focus`	No	Der abgefragte Kode mit allen Detaildaten. Null bei einer Suche und beim Katalog-Einstieg (leerer Kode).
`items`	No	Die Kodeliste der Antwort: bei einer Abfrage die direkt untergeordneten Kodes von 'focus' (bzw. die oberste Ebene bei leerem Kode), bei einer Suche die Treffer.
`parents`	No	Übergeordnete Kodes von 'focus' als Pfad von der obersten Ebene abwärts (Brotkrumen). Leer bei einer Suche und beim Katalog-Einstieg.
`interpretation`	No	Nur bei einer Suche: wie die Suche die Anfrage gelesen hat. Null außerhalb der Suche.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / info

Added value: +{
+  "description": "Was über den Jahrgang zu wissen ist, etwa «Version 2026» (ICD-10-GM 2027) oder «Vorabfassung». Null ohne.",
+  "properties": {
+    "subname": {
+      "description": "Zusatz zum Namen des Jahrgangs, etwa «Version 2026» oder «Vorabfassung». Null ohne Zusatz.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "subnameComment": {
+      "description": "Erläuterung zum Zusatz in einem Satz oder zwei. Null ohne Erläuterung.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

AddedOct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context about result contents: hits appear in 'items' with amount or range, origin (rated vs. hospital-individual), and number of triggering OPS codes. It does not contradict 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.

Conciseness5/5

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

The description is three compact sentences and front-loads the tool's scope before the sibling routing. The result-content sentence is brief and helps orient the agent, despite the existence of an output schema.

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 search tool with 3 parameters, full schema coverage, annotations, and an output schema, the description provides everything needed: purpose, scope, result summary, and explicit sibling routing. No critical context is missing.

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 description coverage is 100%, so the schema already documents query, year, and limit in detail. The description reinforces that the query accepts codes or service descriptions, but it adds no year or limit semantics beyond what the schema provides, making 3 the correct baseline.

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?

The description states a specific verb and resource: searching PEPP additional fees (ZP) by code or service description. It also explicitly distinguishes this tool from ze_search for the DRG system, so an agent can route correctly without comparing schemas.

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?

It names the exact context for this tool (PEPP ZP) and the alternative for DRG additional fees: 'Für Zusatzentgelte im DRG-System ist ze_search zuständig.' This is explicit when-to-use and when-to-use-another-tool guidance.

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?