Skip to main content
Glama
bundeswahlleiter-mcp

bundeswahlleiter-mcp

bwl_turnout

Retrieve official voter turnout by federal state and nationally for Bundestag elections in 2017, 2021, or 2025.

Instructions

Voter turnout by Land and nationally for a Bundestag election. year: 2017, 2021 or 2025 (default 2025).

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

Input Schema

NameRequiredDescriptionDefault
yearNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden on its own. It discloses useful scope facts (Land and national level, three election years), but never states that the operation is a read-only query, whether any prerequisites exist, or how turnout is defined (eligible vs. registered voters). For a simple lookup this is acceptable but not rich.

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

Conciseness5/5

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

Two short sentences, the purpose first and the parameter detail second, with zero filler. Every clause carries information not present elsewhere.

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 one-parameter read tool with an output schema available, the description covers purpose, geographic scope, valid years, and the default. The remaining ambiguity is definitional (what counts as turnout and whether sub-Land breakdowns are included), which slightly weakens completeness.

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 0% and the schema only declares an optional integer with default 2025, so the description is doing the real work by enumerating the valid values 2017, 2021, and 2025 and restating the default. That fully documents the single parameter; the only gap is not saying what happens if an unsupported year is passed.

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 a specific resource and scope: 'Voter turnout by Land and nationally for a Bundestag election.' That distinguishes it from result-oriented siblings such as bwl_national_results or bwl_party_results by subject matter. It stops short of explicitly naming a sibling it is not, so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended context is implied by 'for a Bundestag election' and by listing the three supported election years, but there is no explicit when-to-use or when-not-to-use statement and no alternative tool is named. An agent can infer this is the turnout source, but the routing guidance is left implicit.

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