Skip to main content
Glama

Lintelly HR Deutschland

Was kostet mich eine Person

arbeitgeberkosten
Read-onlyIdempotent

Germany only. Employer costs (Arbeitgeberkosten) of one employee in Germany per month and year: gross pay plus the employer share of social security (Sozialversicherung) for full-time, part-time, working students (Werkstudent) and mini-jobs (Minijob), with rates, contribution ceilings and sources. In the transition zone (Midijob, Übergangsbereich) it calculates the exact employer share with the official factor F, or only the lower bound for years whose factor F is not yet published.

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": {
      "art": "<art>",
      "brutto_monat": "<brutto_monat>"
    },
    "name": "arbeitgeberkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesType of employment
stichtagNoAny day in the month the costs apply to; the rates valid on that day are used. Default today (YYYY-MM-DD)
brutto_monatYesGross pay per month in euro
pauschsteuerNoMini-job: employer pays the 2 % flat-rate tax, default true
gesetzlich_versichertNoMini-job: person has statutory health insurance, default true

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
    • changedInput schema / properties / stichtag / description
      Previous value: -"Month the costs apply to, default today (YYYY-MM-DD)"New value: +"Any day in the month the costs apply to; the rates valid on that day are used. Default today (YYYY-MM-DD)"
    • addedInput schema / properties / stichtag / 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

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the bar is lower. The description adds useful behavioral detail beyond annotations: it uses rates valid on the requested date, cites rates/ceilings/sources, and explains that Midijob calculations use the official factor F or only a lower bound when F is unpublished.

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 front-loaded with the Germany-only scope and the core calculation, then adds the Midijob nuance. It is dense but appropriately sized; the main downside is a long second sentence that could be split for readability.

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?

Given the output schema and full parameter descriptions, the definition is largely complete for an agent to call this tool correctly. The main missing element is explicit guidance on how this relates to potentially overlapping siblings such as 'minijob'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that the Midijob/Übergangsbereich case is handled specially via the official factor F, which is not obvious from the enum or field descriptions alone.

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?

The description states a specific calculation: employer costs of one employee in Germany per month and year, including gross pay plus employer social-security share, across four employment types. This is much more than a restatement of the name, but it does not explicitly distinguish itself from siblings such as 'minijob' or 'mindestlohn_check', leaving some room for an agent to hesitate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context ('Germany only') and names the employment types covered, which implies when the tool is appropriate. However, it gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as the 'minijob' sibling for rule questions rather than cost calculations.

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.