Skip to main content
Glama

Wer ist zuständig?

wer_ist_zustaendig
Read-onlyIdempotent

Zu einer Postleitzahl: Gemeinde, Kreis, Land, Bundestagswahlkreis, was jede Ebene entscheidet, und die zuständigen Abgeordneten in Landtag, Bundestag und Europäischem Parlament. Mit thema zusätzlich, welche Ebene wofür zuständig ist (z. B. „Schule“, „Tempo 30“, „Müll“), mit Rechtsgrundlage.

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": {
      "plz": "<plz>"
    },
    "name": "wer_ist_zustaendig"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYesDeutsche Postleitzahl mit fünf Ziffern, z. B. „10117“
themaNoOptional: Thema oder Anliegen in Stichworten, z. B. „Schlagloch“, „Kita-Platz“ oder „Mietpreisbremse“

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add value — and it does, by describing the returned content per administrative level and the effect of `thema` (adds which level is competent plus the legal basis). It stops short of saying what happens for an unknown or non-resolvable PLZ, which is the main remaining behavioral gap.

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?

Two sentences with no filler; the postal-code scope is front-loaded and the optional `thema` behavior follows immediately. The second sentence is dense with examples but each clause carries information the agent needs.

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 no output schema, the description has to carry the return shape, and it does so by listing the exact entities returned and the extra competence/legal-basis output under `thema`. Only failure behavior for invalid or unresolvable postal codes is left unaddressed, which is minor for a read-only lookup.

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 the baseline is 3; the description earns an extra point by explaining the semantic consequence of each parameter — `plz` maps the address to all administrative levels, and `thema` triggers a competence-plus-legal-basis answer rather than just an address lookup. That is meaning the schema's short field descriptions do not convey.

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 names a specific input (a German postal code) and enumerates the concrete outputs: municipality, Kreis, Land, Bundestagswahlkreis, what each level decides, and the responsible MPs in Landtag, Bundestag and European Parliament. That is a clear verb+resource statement, but it never contrasts itself with siblings such as `abgeordnete`, so an agent must infer that this is the jurisdiction-lookup path rather than a pure MP search.

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?

Usage is implied rather than stated: the description explains what to pass (`plz`, optionally `thema`) but not when to prefer this tool over `abgeordnete` for MP data or when a topic lookup is or isn't appropriate. No exclusions, prerequisites, or alternative routes are given.

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.

Resources