Lintelly HR Deutschland

Rechtswerte suchen

rechtswerte_suchen

Read-onlyIdempotent

Germany only. Search the register of German employment law values (228 values with norm, official source and review date): minimum wage, mini-job limit, notice periods, probation, holiday, sick pay, maternity protection, retention periods, thresholds. Returns up to 20 matches with key, title, value on the date and status.

Input Schema

Name	Required	Description
`gebiet`	No	Optional area of law
`stichtag`	No	Date the values should apply to, default today (YYYY-MM-DD)
`suchtext`	No	Words to search for, German or key, e.g. Mindestlohn, Urlaub, Aufbewahrung

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.

Changed2 schema fields changedOct 31, 2026

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"
+}

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world safety, so the lower bar applies. The description still adds genuinely useful behavior: a hard cap of 20 matches and the shape of each hit (key, title, value on the date, status). It doesn't say what happens on zero matches or whether results are ranked.

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?

Three sentences, no filler, and the most disqualifying constraint ('Germany only') is front-loaded. The corpus description, searchable topics and return behavior follow in a logical order.

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?

With an output schema present, the description needn't detail return values, and it is nonetheless complete about scope, searchable content and the 20-match cap. Minor gap: no guidance on broadening a search when no results are returned.

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 goes beyond it by enumerating the kinds of values searchable via suchtext (minimum wage, notice periods, retention periods) and by tying results to the date parameter ('value on the date'), which helps an agent choose keywords and set stichtag.

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?

States a concrete verb and resource ('Search the register of German employment law values'), plus the corpus size (228 values), field coverage and jurisdiction scope ('Germany only'). That is enough for an agent to tell it apart from single-value siblings like rechtswert or vertragsbausteine_suchen without opening the schema.

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 'Germany only' scope constraint and the topical examples imply when the tool applies, but there is no explicit when-to-use or when-not-to-use guidance against siblings such as rechtswert (single lookup) or schwellen_check. Usage is inferable rather than stated.

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.