Skip to main content
Glama

Lintelly HR Deutschland

HR-Workflow

workflow_vorlage
Read-onlyIdempotent

German employment law, Germany only: 11 follow-up workflows for HR tasks (HR-Workflows), e.g. payroll input deadline, missing onboarding documents, sick leave with eAU and BEM, maternity protection, probation decision, fixed-term contract signed before start. Each shows the chain 'when ... then ...' with default days and roles. Use it as a template for your own reminders. Without kennung it lists all.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workflow_vorlage"
  }
}

Input Schema

NameRequiredDescriptionDefault
kennungNoKey of the workflow, leave out for the list

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. Changed1 schema field changed
    • changedInput schema / properties / kennung / enum
      Previous value: -[
      -  "lohn-stichtag",
      -  "eintritt-unterlagen",
      -  "austritt-rueckgabe",
      -  "probezeit",
      -  "krankheit",
      -  "mutterschutz",
      -  "resturlaub",
      -  "lesebestaetigung",
      -  "mindestlohn",
      -  "befristung"
      -]New value: +[
      +  "lohn-stichtag",
      +  "eintritt-unterlagen",
      +  "austritt-rueckgabe",
      +  "probezeit",
      +  "krankheit",
      +  "mutterschutz",
      +  "resturlaub",
      +  "lesebestaetigung",
      +  "mindestlohn",
      +  "befristung",
      +  "arbeitszeit"
      +]
  2. Changed1 schema field changed
    • 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"
      +}
  3. First observed

TDQS

A4/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 the safety profile is covered. The description adds real substance beyond them: the geographic/legal jurisdiction (Germany only), the internal structure of each workflow ('when ... then ...' with default days and roles), and the intended use as a template. Remaining gap is minor given a read-only list tool with an output schema.

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?

Front-loads jurisdiction and count, then examples, then the structural promise, then usage. Four dense sentences with no filler; the enum values themselves are not redundantly re-listed in prose.

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?

One optional enum param, full schema coverage, annotations covering safety and an output schema covering returns — the description covers jurisdiction, content shape, and the list-vs-single behavior, which is what's needed. Only the sibling disambiguation is absent.

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% and the single enum parameter is already documented as 'Key of the workflow, leave out for the list'. The description's 'Without kennung it lists all' largely restates that, though it confirms the default behavior. Baseline 3 is appropriate when the schema does the heavy lifting.

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 concrete resource and scope: 11 HR follow-up workflow templates under German employment law, Germany only, each shown as a 'when ... then ...' chain with default days and roles. The verb is implicit (list/retrieve templates) but the 'template for your own reminders' framing makes the artifact type clear. It overlaps thematically with siblings such as mutterschutz, probezeit, befristung and bem_pflicht without saying how it differs from them, which keeps it out of 5 territory.

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?

'Use it as a template for your own reminders' plus 'Without kennung it lists all' gives clear call-shape guidance (browse all vs. fetch one). What's missing is any exclusion: nothing tells the agent when to prefer probezeit or mutterschutz over this workflow view, even though those siblings exist.

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.