Skip to main content
Glama

Abgeordnete am Ort

abgeordnete
Read-onlyIdempotent

Die Abgeordneten für eine Postleitzahl, wahlweise nur einer Ebene (land, bund, eu), mit Partei, Wahlkreis bzw. Fraktion und Profil-Link bei Nexus Politics.

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": "abgeordnete"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYesDeutsche Postleitzahl mit fünf Ziffern, z. B. „10117“
ebeneNoNur diese Ebene; ohne Angabe alle drei

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds value by naming the returned fields (party, constituency/group, profile link), but says nothing about result ordering, empty results for a PLZ, or data source latency.

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?

One tightly packed sentence with the resource and scope front-loaded and return fields trailing. No filler, though the trailing enumeration of output fields could be trimmed or moved to the schema.

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 simple two-parameter read-only lookup with full schema coverage and annotations, the definition supplies enough to call correctly, including what comes back. Only minor gaps (empty-result behavior, alternative tools) remain.

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%, with 'plz' pattern and example and an 'ebene' enum already documented in the schema. The description only echoes the level concept, adding no format or semantic detail beyond structured fields — baseline 3.

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 specific resource and query basis ('Die Abgeordneten für eine Postleitzahl') and enumerates the returned fields (Partei, Wahlkreis/Fraktion, Profil-Link). It is clear what the tool does, but it gives no explicit differentiation from siblings such as 'wer_ist_zustaendig' or 'wahlen', which could plausibly overlap.

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 by 'für eine Postleitzahl' plus the optional level filter, and the schema clarifies that omitting 'ebene' returns all three levels. There is no explicit when-to-use vs alternatives or any exclusion (e.g., when to prefer 'wer_ist_zustaendig'), so guidance remains inferential.

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