Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Abstimmungsverhalten eines MdEP

get_mep_vote
Read-onlyIdempotent

Gibt das Abstimmungsverhalten eines Europaabgeordneten (MdEP) im EU-Parlament zurück — wann er/sie dafür, dagegen oder sich enthalten hat, mit Fraktionsmehrheit zum Vergleich. Alle 27 EU-Länder, alle namentlichen Abstimmungen der Wahlperioden 9 und 10 (ab 15.07.2019) einschließlich Änderungsanträgen, neueste zuerst; Änderungsanträge sind je Zeile gekennzeichnet. Quelle HowTheyVote.eu (Open Database License). 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": {
      "mep_name": "<mep_name>"
    },
    "name": "get_mep_vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Abstimmungen, max. 10. Standard: 5
topicNoOptional: Suchbegriff im Abstimmungstitel (englisch, wie bei HowTheyVote), z. B. 'Artificial Intelligence', 'due diligence'
vote_idNoOptional: HowTheyVote-ID einer Abstimmung, z. B. '166051' (steht in jedem Beleg ep-abst bzw. ep-stimme). Liefert die Stimme zu genau dieser Abstimmung.
mep_nameYesName des MdEP, z. B. 'Manfred Weber'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description goes well beyond them: source (HowTheyVote.eu, ODbL), ordering (neueste zuerst), per-row marking of amendments, and a stable citation ID ([[beleg:…]]) that is verifiable via pruefe_belege. It does not state pagination or failure behavior for unknown MEP names, so it falls short of exhaustive disclosure.

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?

Purpose and scope are front-loaded in a single strong opening clause, but the citation instructions are stated twice ('Zitiere mit genau dieser ID' then 'zitiere mit Kennung und beiden Links') in slightly different terms, and the bracketed '[Ohne KI: …]' note adds noise. The result is denser than necessary for the information conveyed.

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 must carry return-shape information – and it does, describing per-hit Beleg-IDs, Kennung, Beleg-Seite and Original links plus the party-majority comparison column. Sourcing and licensing are also covered, leaving only edge cases (empty results, unknown MEP) undocumented.

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 coverage is 100%, so the schema already documents all four parameters including examples; the description adds only marginal meaning (newest-first ordering interacts with limit, and topic is implicitly English-title based). Baseline 3 applies since the schema carries the parameter burden.

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 ('Gibt das Abstimmungsverhalten eines Europaabgeordneten ... zurück') and immediately enumerates the returned dimensions (dafür/dagegen/Enthaltung plus Fraktionsmehrheit zum Vergleich). Scope boundaries are explicit – EU-Parlament, alle 27 Länder, namentliche Abstimmungen der Wahlperioden 9 und 10 ab 15.07.2019 – which separates it from the Bundestag-oriented sibling get_mdb_vote without ambiguity.

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 scope limits (only roll-call votes from 15.07.2019, only terms 9 and 10) implicitly communicate when the tool applies, and the topic/vote_id parameters hint at narrowing versus listing. However, no alternative sibling (get_mdb_vote, search_mep, get_mep_profile) is named and no explicit 'use this when…' routing is given, so the agent must infer selection from the scope text alone.

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.