Skip to main content
Glama
Sign In

DRGSystem — German medical coding catalogs

by de.drgsystem
OverviewDiscussionsAdmin

Alphabet-Einträge zu einem OPS-Kode

opsalpha_get
Read-onlyIdempotent

Liefert alle Einträge des Alphabetischen Verzeichnisses, die auf einen bestimmten OPS-Kode verweisen — also sämtliche Bezeichnungen, unter denen dieser Kode zu finden ist. Berücksichtigt werden beide Schlüsselnummernfelder des Eintrags.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "opsalpha_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesOPS-Kode, normalisiert oder in amtlicher Schreibweise (z. B. '5470' oder '5-470.0').
yearNoKatalogjahr (z. B. 2026). Leer lassen für das aktuellste verfügbare Jahr.

Output Schema

NameRequiredDescriptionDefault
yearNoKatalogjahr, aus dem die Einträge stammen.
offsetNoAnzahl der übersprungenen Treffer vor dieser Seite.
entriesNoDie Einträge dieser Seite, absteigend nach Trefferqualität sortiert.
totalCountNoGesamtzahl der Treffer, unabhängig von der zurückgegebenen Seite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / entries / items / properties / code
      Removed value: -{
-  "description": "Fortlaufende Satznummer des BfArM innerhalb des Alphabetischen Verzeichnisses. Kein OPS-Kode.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / entries / items / properties / textHighlight
      Removed value: -{
-  "description": "Nur für die Trefferhervorhebung im Web-Katalog: Gewicht je Zeichen von 'text' — wie wörtlich die Suchanfrage das jeweilige Wort getroffen hat. 1,00 das Wort selbst, 0,75 eine Wortform oder ein Präfix, 0,50 ein Bestandteil eines zusammengesetzten Wortes, 0,25 ein Synonym oder ein korrigierter Tippfehler. Null außerhalb einer Textsuche. Über MCP immer null.",
-  "items": {
-    "type": "number"
-  },
-  "type": [
-    "array",
-    "null"
-  ]
-}
  2. Changed1 schema field changed
    • addedOutput schema / properties / entries / items / properties / textHighlight
      Added value: +{
+  "description": "Nur für die Trefferhervorhebung im Web-Katalog: Gewicht je Zeichen von 'text' — wie wörtlich die Suchanfrage das jeweilige Wort getroffen hat. 1,00 das Wort selbst, 0,75 eine Wortform oder ein Präfix, 0,50 ein Bestandteil eines zusammengesetzten Wortes, 0,25 ein Synonym oder ein korrigierter Tippfehler. Null außerhalb einer Textsuche. Über MCP immer null.",
+  "items": {
+    "type": "number"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
  3. First observed

TDQS

A4/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 meaningful behavioral context beyond the annotations: it covers all alphabet entries, considers both Schlüsselnummernfelder, and emphasizes exhaustiveness with 'alle' and 'sämtliche'. Return-format details are handled by the output schema.

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 sentences with no filler. It front-loads the core purpose and then adds the key scoping detail about both Schlüsselnummernfelder; every sentence earns its place.

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?

Given that this is a read-only, idempotent lookup with a simple 2-parameter schema and an output schema, the description is largely complete. It provides the necessary domain behavior (reverse lookup of an OPS code and inclusion of both key fields). It lacks an explicit alternative-routing statement, but that is not essential for correct invocation.

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?

The input schema has 100% description coverage for both parameters, so the schema already documents code normalization and the optional year. The description clarifies the high-level lookup concept but adds no new parameter-level semantics beyond what the 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 uses a specific verb ('Liefert'), a clear resource ('Einträge des Alphabetischen Verzeichnisses'), and a precise lookup criterion ('auf einen bestimmten OPS-Kode verweisen'). It also explains what is returned — all labels under which the code can be found — which differentiates it from an open text search like opsalpha_search.

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 intended use case is implied: use this when you already have a known OPS code and need all alphabetical index entries referencing it. However, the description does not explicitly state when to use this tool instead of alternatives such as opsalpha_search or ops_get, nor does it mention exclusions.

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