Skip to main content
Glama
bundeswahlleiter-mcp

bundeswahlleiter-mcp

bwl_constituency_results

Retrieve official constituency election results for a given year and constituency, including winner, turnout, eligible voters, and party first/second votes ranked by first votes.

Instructions

Results of one constituency: winner, turnout, eligible voters, and per-party first/second votes ranked by first votes. year: 2017, 2021 or 2025. constituency: number 1–299 or (part of) the name, e.g. 1, Flensburg, München-Süd.

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

Input Schema

NameRequiredDescriptionDefault
yearYes
constituencyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 full disclosure burden. It explains the shape of the returned data well, which is useful even though an output schema exists, but it never states that this is a read-only lookup, what happens when a constituency name is ambiguous or out of range, or anything about errors or permissions.

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?

Two compact passages: returned fields first, then the two parameter formats with examples. Every clause earns its place, with only minor friction from the dense comma-separated enumeration of acceptable constituency forms and the mid-sentence line break.

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 two-required-parameter lookup with an output schema, this is nearly complete: both parameters, their accepted value domains, and the returned fields are covered. The only residual gap is edge-case behavior, such as what an ambiguous or non-matching constituency name yields, which matters given partial-name matching is explicitly supported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 carry both parameters, and it does: 'year' is pinned to the enumerated values 2017, 2021 or 2025, and 'constituency' is defined as a number 1-299 or part of a name, with three concrete examples including one with a diacritic and hyphen. This compensates fully for the bare integer/string schema.

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 ('Results of one constituency') and enumerates what the result contains: winner, turnout, eligible voters, and per-party first/second votes ranked by first votes. That scope makes it separable from national- or party-level siblings in principle, though it never explicitly contrasts itself with them, keeping it just below 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?

Usage is implied rather than stated: an agent can infer this is the tool for a single-district lookup when it already knows the district identifier. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for national/party aggregates or for discovering valid constituency numbers, so the guidance is only implicit.

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