Skip to main content
Glama
bundeswahlleiter-mcp

bundeswahlleiter-mcp

bwl_party_results

Retrieve a party's Bundestag election results by year, including national second votes, previous-election comparison, and second-vote share by Land.

Instructions

Results of one party in a Bundestag election: national second votes (with previous-election comparison) and second-vote share by Land. year: 2017, 2021 or 2025. party: e.g. CDU, SPD, AfD, GRÜNE, FDP, Die Linke, BSW.

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": {
      "year": "<year>",
      "party": "<party>"
    },
    "name": "bwl_party_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
partyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the returned content, including previous-election comparison and Land-level second-vote share, but does not discuss permissions, failure behavior, or whether data is cached or live. The presence of an output schema reduces the need to describe return structure in detail.

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 description is short and front-loads the main result content before listing parameter examples. Every sentence is relevant, though the parameter notes read as a compact list rather than a fully integrated explanation.

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 tool with an output schema, the description covers the essential scope and parameter values. It is complete enough to call correctly, with only minor gaps around party-name matching and explicit sibling selection guidance.

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 description coverage is 0%, so the description must compensate. It usefully constrains year to 2017, 2021, or 2025 and gives concrete party examples such as CDU, SPD, AfD, GRÜNE, FDP, Die Linke, and BSW. It does not clarify whether party names are case-sensitive or whether partial or alternative names are accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-and-resource combination: results for one party in a Bundestag election, including national second votes with previous-election comparison and second-vote share by Land. This clearly distinguishes it from sibling tools such as bwl_national_results and bwl_constituency_results by scoping the result to a single party.

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 stated scope and the allowed year values, but the description does not explicitly say when to use this tool versus bwl_national_results or bwl_constituency_results. It also gives no guidance on error cases, such as an unsupported party name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.