Skip to main content
Glama

Lintelly HR Deutschland

Ausgleichsabgabe

ausgleichsabgabe
Read-onlyIdempotent

Compensatory levy for unfilled jobs for severely disabled people under German law (Ausgleichsabgabe, §§ 154, 160 SGB IX), years 2024 to 2026. Takes the jobs and the severely disabled employees per month (or one value for all months) and returns required places, employment rate, rate per place and month, the levy and the 31 March deadline. Only employers with 20 or more jobs on annual average are affected. 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": {
      "arbeitsplaetze": "<arbeitsplaetze>"
    },
    "name": "ausgleichsabgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
jahrNoCalendar year of employment, default the current year
arbeitsplaetzeYesJobs (Arbeitsplätze) of 18 or more hours per week without apprentices and fixed terms up to 8 weeks: one value for every month or 12 values January to December
schwerbehinderteNoSeverely disabled or equivalent employees as counted by the employment agency (angerechnet): one value or 12 monthly values, default 0

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. Changed7 schema fields changed
    • changedInput schema / properties / arbeitsplaetze / items / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / jahr / enum
      Removed value: -[
      -  "2024",
      -  "2025",
      -  "2026"
      -]
    • addedInput schema / properties / jahr / maximum
      Added value: +2026
    • addedInput schema / properties / jahr / minimum
      Added value: +2024
    • changedInput schema / properties / jahr / type
      Previous value: -"string"New value: +"integer"
    • changedInput schema / properties / schwerbehinderte / items / 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"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world calculation. The description adds meaningful domain behavior by explaining the levy calculation outputs and the 31 March deadline, without contradicting 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well front-loaded: purpose, scope, inputs, outputs, and eligibility are established efficiently. Legal citations and output details earn their place, though some details are also present in the schema.

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?

Given the output schema and annotations, the description supplies the remaining critical context: legal domain, applicable years, geographic limitation, employer-size threshold, expected inputs, and calculation outputs. Nothing essential for correct tool selection or invocation is missing.

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 schema already documents jahr, arbeitsplaetze, and schwerbehinderte thoroughly. The description reinforces the monthly-versus-annual input pattern but adds little parameter syntax or format detail beyond the schema.

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 names the specific German levy, its legal basis, the calculation years, the inputs and outputs, and the affected employer group. This is clearly distinguishable from the sibling tools, which cover broader HR/legal topics such as termination, working time, and payroll.

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 clear applicability boundaries: years 2024–2026, Germany only, and only employers with at least 20 jobs on annual average. It does not explicitly route to sibling tools such as schwellen_check or bem_pflicht, so it is strong but not fully comparative.

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.