Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Fraktionen vergleichen

compare_parties
Read-onlyIdempotent

Vergleicht das Abstimmungsverhalten zweier Fraktionen — wie oft stimmen sie gemeinsam, wie oft gegeneinander? Gibt einen Alignment-Score zurück. Jede Beispiel-Abstimmung trägt die Kennung bt-abst für ihr Gesamtergebnis (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": {
      "party_a": "<party_a>",
      "party_b": "<party_b>"
    },
    "name": "compare_parties"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional: nur die jüngsten N Abstimmungen. Standard: alle Abstimmungen der laufenden Wahlperiode 21 (wie get_coalition_score); hat eine Partei dort keine Sitze, alle Perioden mit Hinweis.
topicNoOptional: Thema zum Filtern, z. B. 'Klimaschutz'
party_aYesErste Fraktion, z. B. 'SPD'
party_bYesZweite Fraktion, z. B. 'Grüne'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds real value beyond that by disclosing the citation protocol (bt-abst identifiers, [[beleg:...]] IDs, verification via pruefe_belege), but it does not explain score semantics, result shape, or behavior when one party has no seats (that only lives in the schema).

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 return value are front-loaded in the first two sentences, which is good. However, roughly half the text is repeated citation boilerplate — the Beleg-ID instruction is stated three times in different words, and the bracketed '[Ohne KI: ...]' line is promotional noise that does not help invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should carry more of the return contract; it names an 'Alignment-Score' and per-vote example hits but never describes the score's scale or the result structure. For a two-required-parameter analytical tool, this is adequate but leaves the agent guessing about output shape.

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 are already documented, including topic filtering and the default scope. The description contributes almost nothing parameter-specific beyond 'zweier Fraktionen' implying party_a/party_b, so the baseline 3 applies.

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 opening states a specific verb and resource: it compares the voting behavior of two Fraktionen and returns an alignment score, with concrete framing ('wie oft stimmen sie gemeinsam, wie oft gegeneinander'). It is clearly distinguishable from vote-lookup siblings like get_mdb_vote, though it never explicitly contrasts itself with get_coalition_score or compare_eu_groups.

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: the reader infers this is the tool for a pairwise party comparison, and the description routes follow-up steps to get_beleg (for raw vote counts) and pruefe_belege (for verification). There is no explicit when-to-use/when-not guidance versus get_coalition_score, which is only referenced from inside the schema.

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.