Skip to main content
Glama

Anstehende Wahlen

wahlen
Read-onlyIdempotent

Die nächsten Wahlen (Europa, Bund, Land, Kommune, Bürgermeister); mit Postleitzahl nur die, bei denen dort gewählt wird.

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

Input Schema

NameRequiredDescriptionDefault
plzNoDeutsche Postleitzahl mit fünf Ziffern, z. B. „10117“

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds the meaningful behavioral detail that supplying a postal code restricts results to elections actually held there, but it does not say how far ahead 'nächsten' reaches or whether past elections appear.

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?

A single, front-loaded sentence with a parenthetical scope list and a clause on the filter behavior; nothing is redundant. The semicolon construction is slightly compressed but still parseable.

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 zero-required-parameter read-only lookup with no output schema, the description covers the resource, the levels, and the optional filter's effect. The only real gap is the temporal horizon of 'nächsten', which an agent might need to know but can discover from the call.

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 plz format and pattern are already documented in the schema. The description goes beyond that by explaining the semantic effect of the parameter — it filters to elections where the holder of that postal code can actually vote — which the schema does not convey.

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 precisely ('Die nächsten Wahlen') and enumerates the levels covered (Europa, Bund, Land, Kommune, Bürgermeister), so an agent knows it is an election-calendar lookup rather than a results or voting-record tool. It never names a specific sibling to contrast with, but the resource scope is specific enough to distinguish it from tools like abstimmungen or umfragen.

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 description implies the usage pattern via the plz clause: call without plz for a broad list, call with plz to narrow it. It does not state when to prefer this over related tools (e.g. abstimmungen for vote records) or that plz is optional and what the unfiltered result looks like, leaving that to inference.

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.

Resources