Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Wahlkreisprofil

get_wahlkreis_profile
Read-onlyIdempotent

Gibt einen Wahlkreis-Steckbrief zurück — Bundestag Deutschland (Standard, mit Wahlergebnissen der letzten Bundestagswahlen, direktem Abgeordneten, Swing-Analyse und EU-Kohäsionsförderung 2021-2027 inkl. größter Projekte und Träger) oder Nationalrat Österreich (country='AT', Regionalwahlkreis mit Stimmenanteilen der letzten Nationalratswahlen, kein Direktmandat-Konzept; EU-Förderung auf Landesebene). [Ohne KI: liefert ausschließlich Originaldaten aus amtlichen Quellen.]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_wahlkreis_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoLand: 'DE' (Standard) oder 'AT'
wahlkreis_nrNoOptional: Wahlkreis-Nummer (DE: 1–299)
wahlkreis_nameNoName des Wahlkreises, z. B. 'Duisburg II' (DE) oder 'Salzburg' (AT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: exactly which sections the profile contains, and that the AT variant structurally differs (Regionalwahlkreis, no Direktmandat concept, EU funding reported at Landesebene). It does not say what happens when no identifier is supplied, despite zero required parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loaded with the primary case, but it is delivered as one very long sentence with nested parentheses enumerating a dozen fields, which is hard to parse at a glance. The bracketed 'Ohne KI' note reads as bolted-on boilerplate and its purpose is unclear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 usefully outlines return content, so the main burden is met. However, all three parameters are optional, and the description never states the behavior when neither wahlkreis_nr nor wahlkreis_name is given, nor what happens when the two disagree — a real gap for a lookup tool.

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 would be 3, but the description goes further by explaining that country is not just a label — it switches the entire content model (DE Bundestag vs. AT Nationalrat, EU funding at state rather than project level). This is semantics an agent could not derive from the enum-less string parameter alone.

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 concrete verb and resource ("Gibt einen Wahlkreis-Steckbrief zurück") and enumerates the payload: Wahlergebnisse, direktes Mandat, Swing-Analyse, EU-Kohäsionsförderung. It also separates the DE and AT variants, which is more than a restated name. It never explicitly contrasts with the similarly named siblings (get_wahlkreis_cleavage_profil, get_wahlkreis_prognose), so the boundary is inferable from content but not stated.

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 only implied: the tool is for looking up a constituency profile, with DE as the documented default and country='AT' as the Austria variant. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for related questions. The closing note about original amtliche Quellen is informational, not routing guidance.

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.