Skip to main content
Glama

Quellenkontor HR-Daten

by dev.quellenkontor
OverviewDiscussionsAdmin

Mindestlohn und Minijob-Grenze

hr_mindestlohn
Read-onlyIdempotent

Nur Deutschland. Gesetzlicher Mindestlohn (Euro brutto je Stunde) und Minijob-Grenze, auch Geringfügigkeitsgrenze (Euro je Monat), für einen Stichtag ab 01.01.2015, beschlossene künftige Stufen eingeschlossen. English: Statutory minimum wage (Mindestlohn) and mini-job earnings limit (Geringfügigkeitsgrenze) for any date since 2015.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datumNoStichtag im Format JJJJ-MM-TT. Ohne Angabe gilt der heutige Tag.

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": {
-    "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)"
-    },
-    "gueltig_ab": {
-      "description": "Beginn der Gültigkeit des Werts (Datum)"
-    },
-    "gueltig_bis": {
-      "description": "Ende der Gültigkeit, null solange kein Nachfolger feststeht (Datum oder null)"
-    },
-    "hinweise": {
-      "description": "Grenzen der Werte oder der Berechnung, in Sätzen (Liste)"
-    },
-    "lizenz": {
-      "description": "Nutzungsbedingungen der Werte (Text)"
-    },
-    "mindestlohn_brutto_stunde": {
-      "description": "Euro je Stunde (Dezimal)"
-    },
-    "minijob_grenze_monat": {
-      "description": "Euro je Monat (Ganzzahl)"
-    },
-    "minijob_quelle": {
-      "description": "Quelle der Minijob-Grenze (Objekt)"
-    },
-    "minijob_rechtsgrundlage": {
-      "description": "Rechtsgrundlage der Minijob-Grenze (Text)"
-    },
-    "naechster_wert": {
-      "description": "Die nächste beschlossene Stufe (Objekt oder null)"
-    },
-    "quelle": {
-      "description": "Titel und URL der Primärquelle (Objekt)"
-    },
-    "rechtsgrundlage": {
-      "description": "Gesetz oder Verordnung (Text)"
-    },
-    "stand": {
-      "description": "Tag der letzten Prüfung gegen die Quelle (Datum)"
-    },
-    "vorheriger_wert": {
-      "description": "Die Stufe davor (Objekt oder null)"
-    },
-    "zitat": {
-      "description": "Fertiger Satz mit Wert, Gültigkeit, Rechtsgrundlage und Quelle zum Zitieren (Text)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context: the tool covers only Germany, accepts dates back to 01.01.2015, and includes legislated future minimum-wage stages. No contradiction with annotations.

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?

The description is compact and front-loaded with the key constraint 'Nur Deutschland'. The German and English versions repeat the same information, which is slightly redundant but improves accessibility for multilingual agents without adding significant bulk.

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 simple, single-parameter lookup tool with strong annotations, the description is complete: it states the geographic scope, the exact values returned, the valid date range, and the inclusion of future stages. Nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional datum parameter is already well documented with format and default behavior. The description adds extra meaning by defining the valid date range (from 2015) and noting that future legislated stages are included, which the schema alone does not convey.

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 identifies the resource: Germany's statutory minimum wage (Mindestlohn) and mini-job earnings limit (Geringfügigkeitsgrenze), with the relevant units and date scope. It distinguishes itself from siblings like hr_pflegemindestlohn and hr_minijob_abgaben by naming the exact legal values it returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: Germany only, valid for dates from 2015 onward, including already legislated future increases. It does not explicitly name sibling alternatives or state when not to use it, but the scope is specific enough for an agent to select it appropriately.

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