Brutto-Netto- und Gehaltsrechner

get_salary_and_zulagen_options

Read-onlyIdempotent

DISCOVERY: Liefert für einen Dienstherrn oder Tarifvertrag und eine Gruppe alle Stufen mit Grundgehalt sowie alle wählbaren Stellenzulagen (Polizei, Justiz etc.), Amtszulagen und Familienzuschlags-Regeln.

Input Schema

TableJSON Schema

Name	Required	Description
`gruppe`	Yes	Besoldungs- oder Entgeltgruppe (z. B. 'A9', 'A13', 'E11', 'B2').
`dienstherr`	No	Dienstherr / Bundesland (z. B. 'bayern' bzw. 'by', 'bund', 'nordrhein-westfalen' bzw. 'nrw') – erforderlich wenn employmentType='beamte'.
`period_key`	No	Optionaler Gültigkeitszeitraum / Tarifrunde (z. B. '20260501_'). Standard: aktuellste Tabelle.
`tarifvertrag`	No	Tarifvertrag (z. B. 'tvoed-vka', 'tv-l') – erforderlich wenn employmentType='tarif'.
`employmentType`	Yes	Art des Beschäftigungsverhältnisses: 'beamte' für Besoldung oder 'tarif' für Tarifverträge.

Output Schema

TableJSON Schema

Name	Required	Description
`entity`	No
`gruppe`	No	Besoldungs- oder Entgeltgruppe
`stufen`	No	Tabellen-Grundgehälter je Erfahrungsstufe
`zulage_options`	No	Wählbare Stellenzulagen und Amtszulagen (z. B. Polizeizulage) mit Betrag und ID
`employment_type`	No
`familienzuschlag_info`	No	Regeln und Beträge für Ehe- und Kinderbestandteile des Familienzuschlags

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 26, 2026

removedOutput schema / properties / familienzuschlag

Removed value: -{
-  "description": "Regeln und Beträge für Ehe- und Kinderbestandteile des Familienzuschlags",
-  "type": [
-    "object",
-    "array"
-  ]
-}

changedOutput schema / properties / familienzuschlag_info / type

Previous value: -[
-  "object",
-  "array"
-]New value: +"object"

removedOutput schema / properties / stellenzulagen

Removed value: -{
-  "description": "Wählbare Stellenzulagen und Amtszulagen mit Betrag und ID",
-  "type": [
-    "array",
-    "object"
-  ]
-}

addedOutput schema / properties / stufen / items
```
Added value: +{
+  "type": "object"
+}
```

changedOutput schema / properties / stufen / type

Previous value: -[
-  "array",
-  "object"
-]New value: +"array"

addedOutput schema / properties / zulage_options / items
```
Added value: +{
+  "type": "object"
+}
```

changedOutput schema / properties / zulage_options / type

Previous value: -[
-  "array",
-  "object"
-]New value: +"array"

Changed9 schema fields changedSep 26, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```
addedOutput schema / properties / employment_type
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / entity
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / familienzuschlag / type

Previous value: -"object"New value: +[
+  "object",
+  "array"
+]

addedOutput schema / properties / familienzuschlag_info

Added value: +{
+  "description": "Regeln und Beträge für Ehe- und Kinderbestandteile des Familienzuschlags",
+  "type": [
+    "object",
+    "array"
+  ]
+}

removedOutput schema / properties / stellenzulagen / items

Removed value: -{
-  "properties": {
-    "betrag": {
-      "type": "number"
-    },
-    "id": {
-      "type": "string"
-    },
-    "name": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

changedOutput schema / properties / stellenzulagen / type

Previous value: -"array"New value: +[
+  "array",
+  "object"
+]

changedOutput schema / properties / stufen / type

Previous value: -"object"New value: +[
+  "array",
+  "object"
+]

addedOutput schema / properties / zulage_options

Added value: +{
+  "description": "Wählbare Stellenzulagen und Amtszulagen (z. B. Polizeizulage) mit Betrag und ID",
+  "type": [
+    "array",
+    "object"
+  ]
+}

First observedSep 26, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds the behavioral context that this is a 'DISCOVERY' operation and that it returns a comprehensive set of salary levels and allowances, which is useful but not a major extension beyond the annotations. It does not disclose any limitations or prerequisites beyond what the schema states.

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 a single, front-loaded sentence with no filler. It begins with the 'DISCOVERY' label, immediately conveys the purpose, and lists the output components efficiently. Every word earns its place.

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?

For a tool with 5 parameters (2 required) and an output schema, the description adequately summarizes the returned data (all levels with base salary, allowances, family allowance rules) and the input conditions (employer or collective agreement plus group). It does not explain error handling or edge cases, but these are likely covered by the schema and output schema. The description is complete enough for an agent to understand what to expect.

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 all parameters are already explained (gruppe, dienstherr, tarifvertrag, employmentType, period_key). The description reinforces the either/or relationship between dienstherr and tarifvertrag with 'oder', but adds no new syntactic or format details. Given the high schema coverage, a baseline of 3 is appropriate; the description does not need to compensate.

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 clearly states the tool's function: it delivers all pay grades with base salary and selectable allowances (position, office, family) for a given employer or collective agreement and a group. The 'DISCOVERY' prefix signals a discovery-oriented purpose, distinguishing it from calculation tools. The verb 'Liefert' and the explicit resource (salary options) make the purpose unambiguous.

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?

The description implies usage for exploring available salary components and options, as indicated by 'DISCOVERY' and the listing of allowances. It does not explicitly name sibling tools or state when not to use them, but the nature of the output (options rather than computed values) and the required parameters (employmentType, gruppe) clearly orient the agent toward discovery scenarios. A brief mention of alternatives would push this to 5.

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

All Brutto-Netto- und Gehaltsrechner 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.

Resources

Need Help?