DRGSystem — German medical coding catalogs

Kodierrichtlinie Psychiatrie abrufen

dkr_psych_get

Read-onlyIdempotent

Liefert in 'focus' den Volltext einer Richtlinie der DKR-Psych, in 'parents' ihre Einordnung und in 'items' die untergeordneten Abschnitte. Ohne Nummer aufgerufen liefert die Funktion die Liste der Richtlinien.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dkr_psych_get"
  }
}

Input Schema

Name	Required	Description	Default
`code`	No	Nummer der Richtlinie (z. B. 'PD002' oder 'PP005h'). Leer lassen für die Liste.
`year`	No	Katalogjahr — nur angeben, wenn ausdrücklich eine bestimmte Fassung gebraucht wird. Leer lassen (empfohlen): dann kommt die jüngste Fassung, in der es den Kode gibt, auch für inzwischen entfallene Kodes; welcher Jahrgang das ist, steht in 'year' der Antwort.

Output Schema

Name	Required	Description
`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.

AddedOct 31, 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 adds real value by disclosing the shape of the response (full text in 'focus', classification in 'parents', child sections in 'items') and the list fallback when no code is given.

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?

Two short sentences, no filler, with the return-structure detail first and the no-argument behavior second. Every clause carries information an agent needs.

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 annotations, a full output schema, and 100% parameter coverage, the description only needs to orient the agent — which it does. The one gap is that it doesn't point to dkr_psych_search for discovering codes, which matters in a 40-tool catalogue.

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 the 'year' parameter already carries an unusually thorough explanation of the latest-version fallback. The description only reinforces the 'code' semantics via 'Ohne Nummer aufgerufen', adding nothing the schema doesn't already say, 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?

Names a specific verb+resource (retrieves a DKR-Psych guideline) and even enumerates the response slots ('focus', 'parents', 'items'), plus the no-code list mode. It never names the sibling dkr_psych_search, so the get-vs-search split is only inferable from the naming convention.

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 does state one concrete usage branch: calling without a number returns the guideline list. It gives no explicit routing to dkr_psych_search for finding a code, and no when-not-to-use guidance beyond that single clause.

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?