Lintelly HR Deutschland

Klagefrist nach einer Kündigung

klagefrist

Read-onlyIdempotent

Germany only. Calculate the deadline for an unfair dismissal claim (Klagefrist, Kündigungsschutzklage) in Germany: 3 weeks after the written notice was received (§ 4 KSchG), moved to the next working day if it ends on a weekend or public holiday (§ 222 Abs. 2 ZPO). Applies in small businesses too. Use it to know from when a dismissal can be treated as final.

Input Schema

Name	Required	Description	Default
`zugang`	Yes	Day the written notice was received (YYYY-MM-DD)
`bundesland`	No	Federal state of the company for public holidays (Bundesland), e.g. HE

Output Schema

Name	Required	Description
`stand`	Yes
`fallen`	No
`hinweis`	Yes
`quellen`	Yes
`ergebnis`	Yes	Result of the tool; its fields differ per tool
`rechenweg`	No
`herausgeber`	Yes
`naechster_schritt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedInput schema / properties / zugang / format
```
Added value: +"date"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "ergebnis": {
+      "description": "Result of the tool; its fields differ per tool"
+    },
+    "fallen": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "herausgeber": {
+      "type": "string"
+    },
+    "hinweis": {
+      "type": "string"
+    },
+    "naechster_schritt": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "quellen": {
+      "items": {
+        "properties": {
+          "geprueft_am": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "grund": {
+            "type": "string"
+          },
+          "norm": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "bestätigt",
+              "noch nicht bestätigt",
+              "Prüfung überfällig"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "norm"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rechenweg": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "stand": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ergebnis",
+    "quellen",
+    "hinweis",
+    "stand",
+    "herausgeber"
+  ],
+  "type": "object"
+}

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, yet the description still adds real substance: the three-week computation rule, the weekend/holiday rollover (§ 222 Abs. 2 ZPO), and the small-business applicability caveat. It stops short of saying that the holiday rollover depends on the chosen Bundesland.

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?

Three compact sentences, front-loaded with the jurisdictional restriction and then the operative rule and its use case. Every clause carries information; no filler.

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 an output schema present and full schema coverage, the description needs only to convey the legal rule, scope and intent, which it does. The one loose end is that it never states the holiday rollover is computed from the supplied Bundesland, leaving the link between the two parameters implicit.

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 both parameters, including the full Bundesland enum and its purpose for public holidays, are already documented. The description's phrase 'after the written notice was received' aligns with but does not extend the schema's definition of zugang, 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?

States a specific verb ('calculate') and a precisely named legal resource ('Klagefrist, Kündigungsschutzklage') with the governing rule (3 weeks per § 4 KSchG), so an agent knows exactly what this produces. It does not explicitly distinguish itself from the related sibling kuendigungsfrist_rechnen (statutory notice period), which is a nearby concept an agent could confuse.

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?

Gives a clear usage context ('Use it to know from when a dismissal can be treated as final') and a hard scope limit ('Germany only', 'Applies in small businesses too'). No alternatives or when-not-to-use routing are offered, so the agent must infer that deadline-of-notice-period questions belong to kuendigungsfrist_rechnen.

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

All Lintelly HR Deutschland 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.