Skip to main content
Glama

Quellenkontor HR-Daten

by dev.quellenkontor
OverviewDiscussionsAdmin

Urlaubsanspruch-Rechner

hr_urlaubsanspruch
Read-onlyIdempotent

Nur Deutschland. Berechnet den gesetzlichen Mindesturlaub nach dem Bundesurlaubsgesetz für jede Zahl von Arbeitstagen pro Woche (Teilzeit), optional mit Teilurlaub bei Eintritt oder Austritt im Jahr samt Rundung nach § 5 BUrlG. English: Statutory minimum vacation for part-time work and for joining or leaving during the year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jahrNoKalenderjahr für die Teilurlaubsberechnung. Ohne Angabe das Jahr von Austritt oder Eintritt.
austrittNoEnde des Arbeitsverhältnisses (optional)
eintrittNoBeginn des Arbeitsverhältnisses (optional)
arbeitstage_pro_wocheYesArbeitstage pro Woche, 0,5 bis 6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / austritt / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • removedInput schema / properties / eintritt / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "anspruch_tage_im_jahr": {
-      "description": "Anspruch im betrachteten Jahr, bei Teilurlaub gerundet (Dezimal)"
-    },
-    "anspruch_tage_jahr": {
-      "description": "Gesetzlicher Jahresurlaub in Arbeitstagen (Dezimal)"
-    },
-    "arbeitstage_pro_woche": {
-      "description": "Angegebene Arbeitstage pro Woche (Dezimal)"
-    },
-    "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)"
-    },
-    "formel": {
-      "description": "Die Rechnung in Worten (Text)"
-    },
-    "hinweise": {
-      "description": "Grenzen der Werte oder der Berechnung, in Sätzen (Liste)"
-    },
-    "lizenz": {
-      "description": "Nutzungsbedingungen der Werte (Text)"
-    },
-    "quelle": {
-      "description": "Titel und URL der Quelle, auf der der Wert beruht (Objekt)"
-    },
-    "quellen": {
-      "description": "Alle Normen, auf denen die Antwort beruht, mit Titel und URL (Liste)"
-    },
-    "rechtsgrundlage": {
-      "description": "Paragrafen (Text)"
-    },
-    "stand": {
-      "description": "Tag der letzten Prüfung gegen die Quelle (Datum)"
-    },
-    "teilurlaub": {
-      "description": "Ob § 5 BUrlG greift (Boolesch)"
-    },
-    "volle_monate": {
-      "description": "Volle Monate bei Teilurlaub (Ganzzahl)"
-    },
-    "zitat": {
-      "description": "Fertiger Satz mit Wert, Gültigkeit, Rechtsgrundlage und Quelle zum Zitieren (Text)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so no repetition is needed. The description adds genuinely useful behavior beyond structured data: the jurisdiction restriction ('Nur Deutschland') and, importantly, the legal rounding rule ('samt Rundung nach § 5 BUrlG'), which materially affects the computed result and cannot be inferred from the schema or annotations. A 5 would require output-format or edge-case disclosure.

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 German sentences plus a compact English paraphrase, with the most critical constraint ('Nur Deutschland') front-loaded. Each clause earns its place: legal basis, part-time applicability, mid-year entry/exit option, and the §5 BUrlG rounding rule. The German/English duplication is mild and reasonable given the German title and the need for English-speaking agents to match the tool correctly.

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?

For a read-only calculator with 100% schema parameter coverage and safety carried by annotations, the description covers jurisdiction, legal basis, input categories, and the rounding rule. The main gap is the output format (no output schema exists to carry that burden), though the result — vacation days after legal rounding — is predictable from the tool name. Ambiguous parameter combinations (e.g., both eintritt and austritt supplied, or jahr conflicting with those dates) are unaddressed, keeping this below 5.

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%, so the baseline is 3 even without parameter details in the description. The description does add purpose-level meaning by mapping arbeitstage_pro_woche to 'Teilzeit' and eintritt/austritt to 'Teilurlaub', explaining why those parameters exist. It does not, however, add format, unit, or constraint details beyond what the schema already documents, so it stays at baseline.

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 opens with a specific verb and resource: 'Berechnet den gesetzlichen Mindesturlaub nach dem Bundesurlaubsgesetz' (calculates statutory minimum vacation per the Federal Vacation Act). It also names the exact scope inputs (part-time working days per week, mid-year entry/exit). Among 24 sibling HR calculators, this is the only vacation-entitlement toolaine, and the legal basis plus 'Nur Deutschland' boundary makes confusion with tools like hr_mindestlohn or hr_feiertage impossible.

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?

Clear context is given: Germany only, statutory minimum vacation, part-time scenarios, and partial vacation for entries/exits during the year. The phrase 'gesetzlichen Mindesturlaub' implies this excludes contractually/tariff-agreed vacation above the statutory floorause, though that exclusion is not explicit. No sibling alternatives are named, but the tool's legal domain is so distinct from its siblings that major misrouting is unlikely.

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