Skip to main content
Glama

DRGSystem — German medical coding catalogs

by de.drgsystem

Leistungsgruppe abrufen

lg_get
Read-onlyIdempotent

Liefert in 'focus' eine Leistungsgruppe nach § 135e SGB V mit allen Qualitätskriterien und deren Teilanforderungen, gegliedert nach Anforderungsbereich (personelle und sachliche Ausstattung, sonstige Voraussetzungen, verwandte Leistungsgruppen). Verweise auf andere Leistungsgruppen sind in beide Richtungen aufgelöst. Ohne Kode aufgerufen liefert die Funktion die oberste Gliederungsebene.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoKode der Leistungsgruppe ('LG14'), einer Anforderungsstufe ('LG64A') oder eines Leistungsbereichs ('LB1'). Leer lassen für den vollständigen Katalog; 'items' enthält dann alle Leistungsbereiche mit ihren Leistungsgruppen, die Verschachtelung steht in 'treeDepth'.
yearNoKatalogjahr (z. B. 2026). Leer lassen für das aktuellste verfügbare Jahr.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoNoHerkunft der Daten dieses Jahrgangs: Rechtsgrundlage, Version und Stand der zugrunde liegenden Kataloge sowie Quellen.
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.1/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds useful non-obvious behavior: the result is delivered in 'focus', quality criteria are grouped by Anforderungsbereich, references to other Leistungsgruppen are resolved in both directions, and calling without a code returns the top-level hierarchy. This goes beyond what annotations alone provide.

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 two dense sentences with no filler. It front-loads the primary deliverable and behavior, then adds the conditional no-code case at the end. Every sentence contributes meaningful information.

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 read-only lookup tool with a rich output schema, fully documented optional parameters, and safety annotations, the description covers the non-obvious behavioral aspects: grouping, bidirectional reference resolution, and the no-code fallback. Nothing critical is missing for an agent to call the tool correctly.

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 both parameters with examples and default behavior. The description only echoes the no-code case and adds no additional parameter-level semantics beyond what the input schema provides.

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 opens with a specific verb ('Liefert') and names the exact resource (Leistungsgruppe nach § 135e SGB V) with its content (Qualitätskriterien, Teilanforderungen, Anforderungsbereiche). It also distinguishes this from other catalog siblings by focusing on the LG-specific structure and the no-code top-level behavior.

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?

It gives clear guidance for two call modes: with a code and without a code. However, it never explicitly names lg_search as the alternative for keyword-based lookup or states when an agent should prefer search over get. The guidance is implied by the naming and schema rather than stated in the description.

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