Lintelly HR Deutschland

Mutterschutz-Rechner

mutterschutz

Read-onlyIdempotent

German employment law, Germany only: maternity protection periods (Mutterschutz, MuSchG) from the expected delivery date, protection before and after birth, extension after premature or multiple birth, the ban on dismissal (Kündigungsverbot) and the employer's duties: notify the supervisory authority (Aufsichtsbehörde) and get the maternity pay supplement refunded (Umlage U2). Also covers miscarriage and stillbirth (Fehlgeburt, Totgeburt). Use it when an employee is pregnant, has given birth or lost a pregnancy.

Input Schema

Name	Required	Description
`fall`	No	schwangerschaft (pregnancy or birth) or fehlgeburt (miscarriage or stillbirth). Default schwangerschaft
`geburt`	No	Actual date of birth, leave out while the child is not born (YYYY-MM-DD)
`mehrlinge`	No	Twins or more (12 weeks after birth)
`behinderung`	No	Disability of the child certified within 8 weeks, on request (12 weeks after birth)
`fruehgeburt`	No	Premature birth as medically certified (12 weeks after birth)
`ab_500_gramm`	No	Weight at least 500 grams, then it counts as stillbirth even before week 24
`fehlgeburt_am`	No	Date of the miscarriage or stillbirth (YYYY-MM-DD)
`errechneter_termin`	No	Expected date of delivery from the maternity record; for a stillbirth it extends the period (YYYY-MM-DD)
`schwangerschaftswoche`	No	Week of pregnancy at the miscarriage, the 13th week starts after 12 completed weeks

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.

Changed5 schema fields changedOct 31, 2026

addedInput schema / properties / errechneter_termin / format
```
Added value: +"date"
```
addedInput schema / properties / fehlgeburt_am / format
```
Added value: +"date"
```
addedInput schema / properties / geburt / format
```
Added value: +"date"
```
changedInput schema / properties / schwangerschaftswoche / type
```
Previous value: -"number"New value: +"integer"
```

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.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds material context beyond that: jurisdictional limitation (Germany only) and the substantive legal scope, including that extensions depend on premature/multiple birth or certified disability.

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?

Jurisdiction and core scope are front-loaded, followed by the usage sentence. Dense but every clause names a distinct covered case; slightly long enumeration keeps it from a 5.

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?

An output schema exists and all nine parameters are documented, so the description needn't explain return values or field syntax. What remains unstated is minor: no guidance on which parameters apply to which 'fall' branch, which the agent must infer from schema descriptions.

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% and each parameter already carries a legal explanation, so the schema does the heavy lifting. The description adds no parameter-level detail (e.g. how 'fall' gates the other fields) beyond what the schema states, so baseline 3 applies.

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?

Names a specific resource (maternity protection periods under MuSchG) and enumerates exactly what it computes: pre/post-birth protection, extensions, Kündigungsverbot, employer duties, miscarriage/stillbirth. The 'Germany only' scope plus the topic list makes it instantly distinguishable from every sibling tool.

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?

Explicit trigger condition: 'Use it when an employee is pregnant, has given birth or lost a pregnancy.' Clear context for invocation. It names no alternative tool, but no sibling covers Mutterschutz, so there is little ambiguity to resolve.

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.