Skip to main content
Glama
bundeswahlleiter-mcp

bundeswahlleiter-mcp

bwl_constituencies

Retrieve Bundestag constituency results for 2017, 2021, or 2025, including winner and turnout, with optional Land filter and result limit.

Instructions

List constituencies with winner and turnout. year: 2017, 2021 or 2025. land: optional Land name or number (e.g. Bayern, 2) to filter. limit: 1..299 (default 50).

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>"
    },
    "name": "bwl_constituencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
landNo
yearYes
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description has to carry the behavioral burden: it discloses the filtering scope, the default limit of 50 and the 1..299 ceiling, which is meaningful operational context. It does not state ordering, pagination behavior past the limit, or what happens with an unmatched Land, leaving real gaps for an annotation-free tool.

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 purpose is front-loaded in the first clause, and every subsequent phrase maps to a parameter constraint with no filler. The telegraphic 'year: ... land: ... limit: ...' style is compact though slightly clipped, keeping it just below a 5.

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 an output schema present, the description need not explain return values, and all three parameters plus the one required field are addressed. For a simple filtered-list tool this is close to complete; only ordering and pagination semantics are unaddressed.

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, and it largely does: year is constrained to 2017/2021/2025, land is explained as a Land name or number with a concrete example ('Bayern, 2'), and limit's range and default are given. It only misses edge details such as whether land accepts partial names or invalid input handling.

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 opens with a specific verb and resource ('List constituencies') and states what each entry contains ('winner and turnout'), which is enough to separate it from siblings like bwl_constituency_results. It does not explicitly say how it differs from those siblings, so it falls 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 Guidelines3/5

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

It implicitly tells the agent this is for enumerating constituencies filtered by year and optionally by Land, and the enumerated year values steer correct use. However, it never states when to prefer a sibling such as bwl_constituency_results or bwl_turnout, nor any exclusions or prerequisites.

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