Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Abstimmungsverhalten eines MdB

get_mdb_vote
Read-onlyIdempotent

Gibt das Abstimmungsverhalten eines deutschen Bundestagsabgeordneten zurück — wann er Ja, Nein oder Enthalten gestimmt hat, optional gefiltert nach Thema. Nur Bundestag Deutschland. Jede Abstimmung trägt zwei Kennungen: bt-stimme für die Stimme der Person, bt-abst für das Gesamtergebnis der Abstimmung (Stimmenzahlen in der Zählung von abgeordnetenwatch.de, abrufbar mit get_beleg). Jeder Treffer trägt eine Beleg-ID [[beleg:…]]. Zitiere mit genau dieser ID; die fertige Antwort ist mit pruefe_belege prüfbar. Jeder Treffer nennt am Ende der Antwort Kennung, Beleg-Seite und Original; zitiere mit Kennung und beiden Links wie in der Server-Anleitung. [Ohne KI: liefert ausschließlich Originaldaten aus amtlichen Quellen.]

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": {
      "mdb_name": "<mdb_name>"
    },
    "name": "get_mdb_vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Abstimmungen, max. 10. Standard: 5
topicNoOptional: Thema oder Schlüsselwort zum Filtern, z. B. 'Klimaschutz'
mdb_nameYesName des Abgeordneten, z. B. 'Felix Banaszak' oder 'Banaszak'
wahlperiodeNoOptional: 20 oder 21. Ohne Angabe zählen alle erfassten Wahlperioden; die Antwort nennt die Zahl je Wahlperiode, und jede Abstimmung trägt ihre Wahlperiode.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond them: the two-part identifier scheme (bt-stimme vs. bt-abst), the per-hit Beleg-ID format, and the mandatory citation/verification protocol. It stops short of describing limits on unknown names or result ordering.

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

Conciseness3/5

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

The purpose is front-loaded in the first clause, which is good, but the citation protocol is stated twice — once as the [[beleg:…]] rule and again as 'nennt am Ende der Antwort Kennung, Beleg-Seite und Original' — and the bracketed '[Ohne KI: …]' note is boilerplate. Roughly a third of the text is repeated instruction rather than tool information.

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?

There is no output schema, so the description carries the return-value burden, and it does so reasonably: it explains that each hit carries a vote identifier, an aggregate identifier, a Beleg-ID, and links. Given four simple parameters and full schema coverage, an agent has enough to call and cite correctly; only failure modes and ordering remain unstated.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters (mdb_name, topic, wahlperiode, limit) are already documented in the schema itself. The description only restates that topic filtering is optional and adds no format or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource (returns the voting behavior of a German Bundestag MP) plus the scope qualifier 'Nur Bundestag Deutschland', which separates it from the EU-parliament sibling get_mep_vote without naming it. The output content — Ja/Nein/Enthalten per vote, optionally topic-filtered — is concrete enough that an agent knows exactly what it gets back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives real routing guidance: topic filtering is described as optional, and the description steers the agent downstream to get_beleg for the aggregate vote counts and to pruefe_belege to verify the final answer. What is missing is an explicit when-not/alternative statement (e.g. 'for EU MEPs use get_mep_vote'), so the exclusion is only implied by the country qualifier.

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.