Skip to main content
Glama
Sign In

DRGSystem — German medical coding catalogs

by de.drgsystem
OverviewDiscussionsAdmin

Ergänzende Tagesentgelte durchsuchen

et_search
Read-onlyIdempotent

Durchsucht die ergänzenden Tagesentgelte des PEPP-Entgeltkatalogs (Psychiatrie und Psychosomatik, ET, seit 2015) nach Kode oder Leistung. Die Treffer stehen in 'items' mit der Bewertungsrelation je Tag bzw. ihrer Spanne und den OPS-Kodes.

Input Schema

NameRequiredDescriptionDefault
yearNoKatalogjahr (z. B. 2027). Leer lassen für das aktuellste verfügbare Jahr.
limitNoMaximale Anzahl Treffer, 1 bis 100. Standard 25.
queryYesSuchbegriff: ET-Kode (z. B. 'ET01', 'ET01.04') oder Leistung (z. B. '1:1-Betreuung', 'Intensivbehandlung').

Output Schema

NameRequiredDescriptionDefault
infoNoWas über den Jahrgang zu wissen ist, etwa «Version 2026» (ICD-10-GM 2027) oder «Vorabfassung». Null ohne.
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.
interpretationNoNur bei einer Suche: wie die Suche die Anfrage gelesen hat. Null außerhalb der Suche.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+  ]
+}
  2. Added

TDQS

A3.5/5.0
Behavior3/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 safety behavior is covered. The description adds real value by saying hits are returned in 'items' with the daily valuation ratio or its range plus OPS codes, but it says nothing about empty-result behavior or year fallback beyond what the schema states.

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?

Two sentences, front-loaded with the scope-defining phrase and with zero filler. Slightly dense in the first sentence with parenthetical abbreviations, but nothing is wasted.

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?

With an output schema present, the description needn't explain return values, and it still gestures at the result fields. Scope, domain and search keys are all covered; the only omission is explicit routing relative to et_get.

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 of the three parameters (query, year, limit) is documented with examples and defaults in the schema itself. The description adds no parameter-level detail beyond restating that search is by Kode oder Leistung, so 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?

Names a specific verb (durchsucht) and a precisely scoped resource (ergänzende Tagesentgelte des PEPP-Entgeltkatalogs, Psychiatrie/Psychosomatik, seit 2015) plus the two search keys (Kode oder Leistung). It does not explicitly distinguish itself from the sibling et_get, so the agent must infer search-vs-fetch itself.

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?

The description implies usage (search when you have an ET code or a service name) and states the catalog's temporal coverage, which helps scope expectations. It never states when-not to use it or points to et_get/pepp_search as alternatives, leaving routing to inference.

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
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