Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Wahlergebnisse

get_election_results
Read-onlyIdempotent

Gibt Wahlergebnisse zurück — Bundestagswahl Deutschland (Standard, mit Erst- und Zweitstimmen je Wahlkreis) oder Nationalratswahl Österreich (country='AT', Verhältniswahlrecht ohne Direktmandate — nur Stimmenanteile je Regionalwahlkreis). [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_election_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoWahljahr. Standard: 2025 (DE) bzw. 2024 (AT, letzte Nationalratswahl)
limitNoAnzahl Wahlkreise. Standard: 10
parteiNoOptional: Partei für direkten Vergleich
countryNoLand: 'DE' (Standard, Bundestagswahl) oder 'AT' (Nationalratswahl)
wahlkreisNoOptional: Wahlkreisname, z. B. 'Duisburg II' oder 'Berlin Mitte' (DE) bzw. 'Wien', 'Salzburg' (AT-Regionalwahlkreis)
bundeslandNoOptional (nur DE, Wahljahr 2025): aggregiertes Landesergebnis über alle Wahlkreise des Bundeslands, z. B. 'Sachsen'. Nicht mit wahlkreis/wahlkreis_nr kombinieren.
wahlkreis_nrNoOptional: Wahlkreis-Nummer 1-299 (DE), z. B. 61 für Potsdam

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: results come exclusively from official sources with no AI-generated content, and the AT mode returns only vote shares because there are no direct mandates. It does not describe pagination or return structure, so the added value is real but moderate.

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?

The core purpose and the country switch are front-loaded in a single sentence, with the provenance note bracketed at the end. Dense parenthetical nesting makes it slightly harder to scan, but no sentence is filler and every clause carries information.

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 seven optional parameters, no output schema and no enums, the description does the important work: it establishes the two data regimes and the official-source provenance. Parameter details are fully carried by the schema, so nothing critical is missing. Return formatting is only hinted at rather than stated, which keeps it short of a 5.

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, but the description goes beyond the schema by explaining what country='AT' changes in the returned data (Verhältniswahlrecht without Direktmandate, only Stimmenanteile per Regionalwahlkreis) versus the German Erst-/Zweitstimmen. That is output-shaping semantics the schema alone does not convey. The remaining parameters (year, limit, partei, wahlkreis, bundesland, wahlkreis_nr) get no added meaning in the description, which keeps it from a 5.

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 the resource (Wahlergebnisse) and specifies the two electoral systems it covers: Bundestagswahl Germany with Erst-/Zweitstimmen per Wahlkreis, and Nationalratswahl Austria via country='AT' with Stimmenanteile per Regionalwahlkreis. It is specific enough for an agent to know this returns official election results rather than polls or vote records. It does not name a sibling (e.g. get_swing_wahlkreise or get_aktuelle_umfragen), so sibling differentiation is left implicit.

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 the country switch: default is the German Bundestagswahl, and country='AT' selects the Austrian Nationalratswahl with its different data shape. That gives the agent a clear selector between the two modes. There is no explicit when-to-use/when-not-to-use guidance, and no mention of when to prefer this over related tools such as polling or swing-district tools.

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.