Skip to main content
Glama

Quellenkontor HR-Daten

by dev.quellenkontor
OverviewDiscussionsAdmin

Kündigungsfristen-Rechner

hr_kuendigungsfrist
Read-onlyIdempotent

Nur Deutschland. Berechnet die gesetzliche Kündigungsfrist nach § 622 BGB und den Tag, an dem das Arbeitsverhältnis endet, aus Eintrittsdatum und Zugang der Kündigung, mit Probezeit und Seite (Arbeitgeber oder Arbeitnehmer). English: Statutory notice period and end date under § 622 BGB from start date and date of receipt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seiteNoWer kündigt. Standard: arbeitgeber
zugangYesTag, an dem die Kündigung zugeht, nicht vor dem Eintritt
eintrittYesBeginn des Arbeitsverhältnisses
probezeitNotrue, wenn eine Probezeit vereinbart ist. Standard: false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / eintritt / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • removedInput schema / properties / zugang / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "betriebszugehoerigkeit_jahre": {
-      "description": "Volle Jahre bis zum Zugang (Ganzzahl)"
-    },
-    "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)"
-    },
-    "eintritt": {
-      "description": "Beginn des Arbeitsverhältnisses (Datum)"
-    },
-    "ende": {
-      "description": "Tag, an dem das Arbeitsverhältnis endet (Datum)"
-    },
-    "frist": {
-      "description": "Die Frist in Worten (Text)"
-    },
-    "frist_code": {
-      "description": "Maschinenlesbare Kennung der Frist (Text)"
-    },
-    "fristende": {
-      "description": "Ende der reinen Frist (Datum)"
-    },
-    "hinweise": {
-      "description": "Grenzen der Berechnung (Liste)"
-    },
-    "lizenz": {
-      "description": "Nutzungsbedingungen der Werte (Text)"
-    },
-    "probezeit": {
-      "description": "Ob die Probezeitfrist angewendet wurde (Boolesch)"
-    },
-    "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": "Absatz und Nummer in § 622 BGB (Text)"
-    },
-    "seite": {
-      "description": "arbeitgeber oder arbeitnehmer (Text)"
-    },
-    "stand": {
-      "description": "Tag der letzten Prüfung gegen die Quelle (Datum)"
-    },
-    "zitat": {
-      "description": "Fertiger Satz mit Wert, Gültigkeit, Rechtsgrundlage und Quelle zum Zitieren (Text)"
-    },
-    "zugang": {
-      "description": "Tag, an dem die Kündigung zugeht (Datum)"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the legal basis and country restriction, and clarifies it computes statutory (not contractual) notice periods. It does not contradict annotations and provides useful context beyond the annotations.

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 (German and English), front-loaded with the core function, and contains no filler. Every word serves a purpose, making it efficient and easy to parse.

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 no output schema, the description adequately conveys inputs and what it returns (notice period and end date). It could specify the output format (e.g., months or date) but the intent is clear. Given the simplicity and annotation coverage, the description is complete enough.

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 coverage is 100%, so all parameters are already documented in the schema with descriptions. The description only restates parameter names (Eintrittsdatum, Zugang, Probezeit, Seite) without adding additional meaning or clarifying edge cases. Baseline 3 is appropriate since the schema carries the semantic load.

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 calculates the statutory notice period and end date under § 622 BGB, with specific inputs (start date, receipt date) and options (probezeit, Seite). It names the legal basis and distinguishes this tool from siblings like hr_urlaubsanspruch or hr_mindestlohn, which cover different HR topics.

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 explicitly restricts to Germany ('Nur Deutschland') but does not explicitly mention alternatives or exclusions. However, given the sibling list, this is the only tool for notice periods, so usage context is clear enough. It could have stated 'use for statutory notice period calculations' but the purpose implies it.

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