Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Swing-Wahlkreise

get_swing_wahlkreise
Read-onlyIdempotent

Listet die instabilsten Wahlkreise nach Wechselwähler-Potenzial (Swing-Score 0-1). Ideal für Wahlkampf-Ressourcenallokation: Wo lohnen sich Investitionen? Berechnet aus Erststimmen-Margin 2025, demografischem Drift und Cleavage-Volatilität. Optional nach Bundesland oder Swing-Richtung filterbar — Swing-Richtung ist die profitierende Partei (z. B. 'AfD'), KEIN Von-Partei-Paar; 'CDU→AfD' wird toleriert, aber nur der Teil nach dem Pfeil ('AfD') wird tatsächlich gematcht. [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_swing_wahlkreise"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl WK, max. 50. Standard: 20
parteiNoOptional: Nur WK wo Swing-Richtung diese Partei betrifft, z. B. 'AfD', 'SPD'
min_scoreNoMindest-Swing-Score 0,0–1,0. Standard: 0. Ab 0,65 gilt ein Wahlkreis als instabil, ab 0,50 als erhöht — 0,65 ist daher der sinnvolle Einstieg.
bundeslandNoOptional: Nur WK in diesem Bundesland, z. B. 'Bayern', 'NRW'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds real value beyond that: the score is derived from Erststimmen-Margin 2025, demographic drift, and cleavage volatility, and the bracketed note declares an amtliche-Quellen provenance with no AI synthesis. It still says nothing about ordering ties or result volume, but for a read-only list tool this is solid.

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?

Purpose, use case, and computation basis are front-loaded in that order, and the arrow-handling caveat sits right where it matters. The closing provenance bracket is slightly tangential but brief, so overall the text earns its length.

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?

There is no output schema, and the description compensates by defining the swing score's range and the 0.65 / 0.50 instability thresholds an agent needs to interpret results. It does not enumerate the returned fields, which is the remaining gap for a tool with no output schema.

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%, giving a baseline of 3, but the description genuinely extends parameter meaning: it warns that Swing-Richtung is the benefiting party and not a from-party pair, and explains that 'CDU→AfD' is tolerated with only 'AfD' actually matched. That resolves an ambiguity the schema text alone leaves open. It adds nothing further about limit or bundesland, which the schema already covers.

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?

"Listet die instabilsten Wahlkreise nach Wechselwähler-Potenzial (Swing-Score 0-1)" gives a specific verb, resource, and ranking metric, so the agent knows exactly what comes back. It does not name a sibling such as rank_wahlkreise to separate itself from, which keeps it short of a 5.

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?

"Ideal für Wahlkampf-Ressourcenallokation: Wo lohnen sich Investitionen?" states the intended use case clearly, and the min_score note ("ab 0,65 ... daher der sinnvolle Einstieg") gives concrete operational guidance. It offers no explicit exclusions or named alternative tools, so 4 rather than 5.

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