Brutto-Netto- und Gehaltsrechner

get_public_sector_options

Read-onlyIdempotent

Liefert eine Übersicht aller Dienstherren (Bund & 16 Bundesländer) und Tarifverträge (TVöD, TV-L, etc.) mit den verfügbaren Besoldungsgruppen.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tarif`	No	Liste aller Tarifverträge im Öffentlichen Dienst (z. B. TVöD VKA, TV-L)
`aerzte`	No	Liste aller Ärztetarife im Öffentlichen Dienst
`beamte`	No	Liste aller Dienstherren für Beamte (Bund und alle 16 Bundesländer)

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 26, 2026

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

changedOutput schema / properties / aerzte / type

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

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

changedOutput schema / properties / beamte / type

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

removedOutput schema / properties / dienstherren

Removed value: -{
-  "description": "Liste aller Dienstherren für Beamte (Bund und alle 16 Bundesländer)",
-  "type": [
-    "array",
-    "object"
-  ]
-}

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

changedOutput schema / properties / tarif / type

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

removedOutput schema / properties / tarifvertraege

Removed value: -{
-  "description": "Liste aller Tarifverträge im Öffentlichen Dienst (z. B. TVöD VKA, TV-L)",
-  "type": [
-    "array",
-    "object"
-  ]
-}

Changed9 schema fields changedSep 26, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / aerzte

Added value: +{
+  "description": "Liste aller Ärztetarife im Öffentlichen Dienst",
+  "type": [
+    "array",
+    "object"
+  ]
+}

addedOutput schema / properties / beamte

Added value: +{
+  "description": "Liste aller Dienstherren für Beamte (Bund und alle 16 Bundesländer)",
+  "type": [
+    "array",
+    "object"
+  ]
+}

removedOutput schema / properties / dienstherren / items
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / dienstherren / type

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

removedOutput schema / properties / perioden

Removed value: -{
-  "description": "Verfügbare Gültigkeitszeiträume und Tarifrunden",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / tarif

Added value: +{
+  "description": "Liste aller Tarifverträge im Öffentlichen Dienst (z. B. TVöD VKA, TV-L)",
+  "type": [
+    "array",
+    "object"
+  ]
+}

removedOutput schema / properties / tarifvertraege / items
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / tarifvertraege / type

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

First observedSep 26, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the content scope (employers, agreements, salary groups) but does not disclose additional behavioral traits such as auth requirements or rate limits. Since annotations cover the safety profile, a score of 3 is appropriate.

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, concise sentence that front-loads the purpose. There is no redundancy or unnecessary detail.

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?

The tool is simple with no parameters, and the output schema exists (though not shown). The description fully explains what the tool returns, and annotations cover safety. Nothing is missing for an agent to call it correctly.

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?

The tool has zero parameters, so schema coverage is trivially 100%. The description does not need to explain parameters, and the baseline for 0 params is 4.

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 provides an overview of all employers (federal and 16 states) and collective agreements with available salary groups. It uses a specific verb and resource, and clearly distinguishes from sibling tools that calculate salaries.

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 does not explicitly state when to use this tool versus alternatives. It implies usage as a read-only overview tool, but does not mention alternatives or exclusions, so an agent must infer. Given the sibling tools are for salary calculation, the usage context is implied but not explicit.

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?