Skip to main content
Glama

DRGSystem — German medical coding catalogs

by de.drgsystem

Fallpauschale abrufen

drg_get
Read-onlyIdempotent

Liefert in 'focus' alles, was der Fallpauschalenkatalog zu einer DRG ausweist: die Werte jeder Anlage, in der sie geführt wird (Bewertungsrelationen für Haupt- und Belegabteilung, Verweildauergrenzen mit Zu- und Abschlägen, Pflegeerlös, Verlegungs- und Wiederaufnahmekennzeichen), die zugehörigen Fußnoten im Volltext und die daneben abrechenbaren Zusatzentgelte. Ohne Kode aufgerufen liefert die Funktion die oberste Ebene (MDC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoDRG-Kode (z. B. 'F01A') oder MDC-Gruppe. Leer lassen für die oberste Ebene des Katalogs.
yearNoKatalogjahr (z. B. 2026). Leer lassen für das aktuellste verfügbare Jahr.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoKatalogjahr, aus dem alle Daten dieser Antwort stammen.
focusNoDer abgefragte Kode mit allen Detaildaten. Null bei einer Suche und beim Katalog-Einstieg (leerer Kode).
itemsNoDie Kodeliste der Antwort: bei einer Abfrage die direkt untergeordneten Kodes von 'focus' (bzw. die oberste Ebene bei leerem Kode), bei einer Suche die Treffer.
parentsNoÜbergeordnete Kodes von 'focus' als Pfad von der obersten Ebene abwärts (Brotkrumen). Leer bei einer Suche und beim Katalog-Einstieg.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so no safety ambiguity exists. The description adds meaningful behavioral context: that a null/empty code triggers a different behavior (returning the top-level MDC), and that the response contains not just a single value but a composition of all catalog details, footnotes, and supplementary fees. It is transparent about the conditional behavior without contradicting 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 a single, dense sentence that enumerates the full return payload without fluff, and ends with the crucial empty-code behavior. Every clause adds information; no content 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?

The output schema is present, so the exact return shape is already structured. Annotations cover read-only and idempotent behavior. The description adds the remaining contextual glue: how the input parameter changes the scope and what content areas are included. For a read-only GET-style lookup with two optional parameters and an output schema, this is 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 both parameters (code, year) are clearly documented in the schema with examples and defaults. The description reinforces that 'code' is the primary semantic driver ('Ohne Kode aufgerufen...'), which adds a little context beyond the schema, but does not significantly change the baseline of 3.

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 begins with a specific verb ('Liefert') and names the exact resource (Fallpauschalenkatalog) and the primary access key (DRG), enumerating the returned data fields. It also contrasts itself with sibling search tools by stating that a code is required to get details, otherwise it returns the top-level MDC.

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?

The description clearly explains the two invocation modes: with a DRG code for detailed catalog data, and without a code for the MDC top level. It does not explicitly name alternatives like drg_search or other lookup tools, but the 'Ohne Kode aufgerufen...' sentence provides solid usage context for when to call this tool.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool is explicitly paired with a search and a get operation per catalog, with distinct roles: search returns hits, get returns full records plus hierarchy. Potential confusion between ICD/OPS systematic and alphabetic searches is actively resolved in the descriptions by cross-referencing exactly when to use each.

Naming Consistency5/5

The vast majority of tools follow a predictable <catalog>_search and <catalog>_get pattern, with alphabetic variants like icd10alpha_search/icd10alpha_get. The single exception, lg_ops_strukturmerkmale, is still descriptive and clearly tied to the Leistungsgruppe domain, so the overall naming remains coherent.

Tool Count4/5

At exactly 25 tools, the server sits at the heavy end of the typical range, but each pair covers a distinct official German medical coding catalog or reference work. Given the broad scope—ATC, ICD, OPS, DRG, PEPP, DKR, SEG-4, hospitals, Leistungsgruppen, and Zusatzentgelte—the count is justified rather than bloated.

Completeness5/5

The server provides consistent search and full-record retrieval for every catalog it exposes, including alphabetic indexes where relevant and hierarchy browsing via get-without-code. Cross-references between ICD, OPS, DRG, ATC, DKR, and SEG-4 are integrated into the get operations, so there are no obvious dead ends for the domain.

Resources