Skip to main content
Glama

Quellenkontor HR-Daten

by dev.quellenkontor
OverviewDiscussionsAdmin

Pflegemindestlohn

hr_pflegemindestlohn
Read-onlyIdempotent

Nur Deutschland. Pflegemindestlohn in Euro brutto je Stunde für Pflegehilfskräfte, Pflegekräfte mit mindestens einjähriger Ausbildung und Pflegefachkräfte an einem Stichtag ab 2015, bis 2021 auch Ost, dazu der zusätzliche Urlaub nach der … English: Minimum wages in long-term care (Pflegemindestlohn) by qualification, plus extra vacation, since 2015.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datumNoStichtag im Format JJJJ-MM-TT. Ohne Angabe gilt der heutige Tag.
bestandteilNoNur diesen Bestandteil liefern und zitieren, etwa für eine einzelne Frage (optional). Erlaubt sind die ids der Bestandteile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / datum / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "bestandteile": {
-      "description": "Je Qualifikation Betrag, Gültigkeit, Verordnung und Quelle (Liste)"
-    },
-    "datensatz": {
-      "description": "Kennung des Datensatzes (Text)"
-    },
-    "datenstand": {
-      "description": "Kennung des Datenstands: Datum und laufende Nummer der letzten Änderung im Änderungsprotokoll (/v1/aenderungen), die diesen Datensatz betrifft. Gleicher Datenstand heißt unveränderter Inhalt, praktisch für Prüfer und zum Vergleich zweier Abfragen (Text)"
-    },
-    "datum": {
-      "description": "Abgefragter Stichtag (Datum)"
-    },
-    "hinweise": {
-      "description": "Grenzen der Werte oder der Berechnung, in Sätzen (Liste)"
-    },
-    "lizenz": {
-      "description": "Nutzungsbedingungen der Werte (Text)"
-    },
-    "regeln": {
-      "description": "Geltungsbereich und Regeln aus der Verordnung (Liste)"
-    },
-    "stand": {
-      "description": "Tag der letzten Prüfung gegen die Quelle (Datum)"
-    },
-    "vorlaeufig": {
-      "description": "true, wenn für den Stichtag noch nicht alle Werte festgelegt sind (Boolesch)"
-    },
-    "werte": {
-      "additionalProperties": true,
-      "description": "Kurzform: Bestandteil und Wert am Stichtag, null solange ein angekündigter Wert fehlt",
-      "properties": {
-        "pflegefachkraft": {
-          "description": "Mindestlohn für Pflegefachkräfte, Euro je Stunde",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "pflegehilfskraft": {
-          "description": "Mindestlohn für Pflegehilfskräfte, Euro je Stunde",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "pflegehilfskraft_ost": {
-          "description": "Mindestlohn für Pflegehilfskräfte im Ostgebiet ohne Berlin (bis 31.08.2021), Euro je Stunde",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "qualifizierte_pflegehilfskraft": {
-          "description": "Mindestlohn für Pflegekräfte mit mindestens einjähriger Ausbildung, Euro je Stunde",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "qualifizierte_pflegehilfskraft_ost": {
-          "description": "Mindestlohn für Pflegekräfte mit mindestens einjähriger Ausbildung im Ostgebiet ohne Berlin (bis 31.08.2021), Euro je Stunde",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "zusatzurlaub_tage": {
-          "description": "Mehrurlaub je Kalenderjahr bei Fünf-Tage-Woche, Tage",
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "zitat": {
-      "description": "Fertiger Satz mit Wert, Gültigkeit, Rechtsgrundlage und Quelle zum Zitieren (Text)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

B3.4/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 destructiveHint=false, covering the safety profile. The description adds context about the data range (since 2015, East Germany until 2021) and extra vacation, but does not disclose additional behavioral aspects like rate limits or response format. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is fairly concise but has a truncated part ('nach der …') that leaves the sentence incomplete. It mixes German and English, which is acceptable but not ideal. The key information is front-loaded, but the incomplete phrase detracts from structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is incomplete due to the truncation, and it does not explain what the tool returns (e.g., a value, a list, or a breakdown). Given the tool's complexity (multiple qualifications, date-based values, extra vacation), the description lacks sufficient detail to fully guide an agent. No output schema exists, so the description should compensate, but it falls short.

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% for both parameters (datum and bestandteil), with clear descriptions in the schema. The description mentions 'by qualification' which aligns with the bestandteil enum but does not add new information beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool provides minimum wages in long-term care (Pflegemindestlohn) for Germany, broken down by qualification, plus extra vacation, since 2015. It uses a specific verb ('provides' implied) and resource, and the mention of 'Pflegemindestlohn' distinguishes it from general minimum wage tools like hr_mindestlohn.

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 for long-term care minimum wage queries but does not explicitly state when to use this tool versus alternatives like hr_mindestlohn or hr_mindestausbildungsverguetung. It mentions 'Nur Deutschland' but no explicit when/when-not guidance or alternative names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Quellenkontor HR-Daten 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