Skip to main content
Glama

Lintelly HR Deutschland

Urlaubsabgeltung

urlaubsabgeltung
Read-onlyIdempotent

Payment in lieu of untaken holiday when employment ends under German law (Urlaubsabgeltung, § 7 Abs. 4 and § 11 BUrlG). Calculates the holiday entitlement in the year of leaving (full or partial, Teilurlaub), adds carry-over, subtracts days taken and multiplies the open days by the daily rate from the last 13 weeks' pay. Use it when someone leaves with holiday left. Germany only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tage_pro_woche": "<tage_pro_woche>"
    },
    "name": "urlaubsabgeltung"
  }
}

Input Schema

NameRequiredDescriptionDefault
austrittNoLast day of employment (YYYY-MM-DD)
eintrittNoFirst day of employment (YYYY-MM-DD)
offene_tageNoOpen holiday days if already known; then entry and exit dates are not needed
jahresurlaubNoContractual annual holiday for full time in a 5-day week, in days (legal minimum 20)
rest_vorjahrNoHoliday carried over from the previous year that has not lapsed. Leave out to add partial holiday from the year of entry automatically where it applies
schon_genommenNoHoliday days already taken in the year of leaving
tage_pro_wocheYesWorking days per week of the person, 0.5 to 6
schwerbehindertNoTrue if the person is severely disabled; the additional holiday (§ 208 SGB IX) is paid out too
variabel_13_wochenNoVariable pay (commission, allowances) in the last 13 weeks in euros, without overtime pay
monatsgehalt_bruttoNoFixed gross monthly salary in euros
verdienst_13_wochenNoAlternative to the monthly salary: gross pay of the last 13 weeks in euros, without overtime pay and one-off payments
mehrurlaub_gezwoelfteltNoTrue only if the contract expressly reduces holiday above the legal minimum pro rata (1/12 per month) when leaving

Output Schema

NameRequiredDescriptionDefault
standYes
fallenNo
hinweisYes
quellenYes
ergebnisYesResult of the tool; its fields differ per tool
rechenwegNo
herausgeberYes
naechster_schrittNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / austritt / format
      Added value: +"date"
    • addedInput schema / properties / eintritt / 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"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds substantial context: legal basis, full/partial entitlement, carry-over, subtraction of taken days, and daily-rate calculation from the last 13 weeks' pay. It also specifies the German-law scope and leaving scenario.

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 three tight sentences: purpose and legal basis first, calculation logic second, usage and jurisdiction last. Every sentence earns its place and nothing is redundant.

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 complex twelve-parameter calculation tool with full schema descriptions and an output schema, the description supplies the necessary legal context, calculation outline, use case, and jurisdiction. The remaining details, such as parameter relationships and return values, are covered by the rich schema and output schema.

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 the schema already documents all twelve parameters thoroughly. The description adds conceptual clarity by mentioning carry-over and subtracting days taken, but it does not explain individual parameters or the offene_tage alternative to entry/exit dates; the schema does that.

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 states a specific verb and resource: it calculates payment in lieu of untaken holiday when employment ends under German law. The employment-end scenario distinguishes it from ongoing holiday entitlement and forfeiture siblings such as urlaubsanspruch and urlaubsverfall_hinweis.

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?

It gives explicit usage guidance: 'Use it when someone leaves with holiday left' and 'Germany only.' It does not name alternatives or state when not to use it, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.