DRGSystem — German medical coding catalogs

Landesbasisfallwerte suchen

basisfallwerte_search

Read-onlyIdempotent

Sucht den Landesbasisfallwert eines Bundeslandes nach Name oder Kürzel (z. B. 'Bayern', 'NW'). Jeder Treffer in 'items' nennt den abrechenbaren Landesbasisfallwert des Jahres, die Veränderung zum Vorjahr und den Abstand zum Bundesbasisfallwert; 'bund' enthält den Bundesbasisfallwert mit Korridor. Passt kein Land, stehen alle 16 in 'items'.

Input Schema

Name	Required	Description
`year`	No	Jahr (z. B. 2026). Leer lassen für das aktuellste verfügbare Jahr.
`limit`	No	Wird ignoriert: es gibt höchstens 16 Länder.
`query`	Yes	Name oder Kürzel des Bundeslandes (ISO 3166-2:DE ohne 'DE-'), z. B. 'Hessen' oder 'HE'.

Output Schema

Name	Required	Description
`bund`	No	Bundesbasisfallwert des Jahres mit Korridor und Verlauf — Bezugsgröße aller Landesbasisfallwerte.
`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"
+  ]
+}

AddedSep 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered; the description still adds real context by describing each item's fields (abrechenbarer Wert, Veränderung zum Vorjahr, Abstand zum Bund) and the 'bund' object with Korridor. It does not mention pagination or ordering, which is a minor gap for a capped 16-row result.

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?

Three sentences, zero filler, with the lookup semantics front-loaded and the return shape and fallback following in order of importance. Nothing repeats the schema verbatim.

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?

An output schema exists, yet the description still usefully names the returned fields and the whitelist-style fallback, which is the main surprising behavior. Only the absence of any cross-reference to the *_get sibling keeps it from being fully complete.

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% and each parameter is already documented there, including the 'limit is ignored' note. The description reinforces the query semantics with examples ('Bayern', 'NW') but adds no format or constraint information beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Sucht den Landesbasisfallwert eines Bundeslandes') plus the query form (Name oder Kürzel mit Beispielen). The search-vs-get split against the sibling basisfallwerte_get is implied by the query-based lookup but never made explicit.

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

Usage Guidelines3/5

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

Explains the fallback behavior ('Passt kein Land, stehen alle 16 in items'), which tells the agent what happens on a miss, but gives no explicit guidance on when this tool should be chosen over basisfallwerte_get or how to treat the year parameter beyond the schema note.

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?