Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Koalitions-Score

get_coalition_score
Read-onlyIdempotent

CoalitionSimulator™ — Berechnet den Koalitions-Readiness-Score zweier Parteien aus: (1) Abstimmungs-Alignment im Bundestag (60% Gewicht) + (2) Versprechen-Themen-Überlapp aus Wahlprogrammen (40% Gewicht). Score 0–100%. Zeigt Top-5 gemeinsame Themen und Abstimmungs-Divergenz. Ideal für Journalisten, Politologen und Koalitions-Analyse nach Wahlen. [🤖 KI-Einsatz (EXTRAHIERT, Claude Haiku 4.5): Die Schnittmengen-Berechnung beruht auf maschinell extrahierten Wahlversprechen.]

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

Input Schema

NameRequiredDescriptionDefault
topicNoOptional: Thema filtern, z. B. 'Klimaschutz', 'Wirtschaft'
party_aYesErste Partei: SPD, CDU/CSU, Grüne, FDP, AfD, Linke, BSW
party_bYesZweite Partei: SPD, CDU/CSU, Grüne, FDP, AfD, Linke, BSW

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 closed-world, so the safety bar is covered. The description adds real value beyond that: the scoring formula and weights, the 0–100% output range, the specific returned artifacts (top-5 shared topics, voting divergence), and an explicit data-provenance caveat that the promise overlaps come from machine extraction by Claude Haiku 4.5 — that last point is a genuine trust caveat an agent would not otherwise know.

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?

Front-loaded and dense: the method and weights come before the audience note and the provenance caveat. The 'CoalitionSimulator™' branding and the journalist/political-scientist audience sentence are the least load-bearing parts, but they cost little and the whole thing stays a single compact block.

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?

With no output schema, the description carries the return-value burden and does so: score range, the top-5 topics, and the divergence breakdown are all named. Combined with a fully documented three-parameter schema and complete annotations, an agent has what it needs to call this correctly; only execution-level details (latency, how divergence is formatted) are absent.

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 party_a, party_b and the optional topic filter are already fully documented with valid values and an example. The description adds nothing parameter-level beyond noting that the parties are compared pairwise; the baseline of 3 is appropriate when the schema does the work.

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: it computes a coalition readiness score for two named parties, and it spells out the two weighted components (60% Bundestag voting alignment, 40% election-programme overlap). No sibling tool produces a composite two-party score, so an agent can distinguish it immediately.

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 phrase 'Ideal für Journalisten, Politologen und Koalitions-Analyse nach Wahlen' gives a use context (post-election coalition analysis) but is framed as an audience pitch rather than an operational rule. It never names an alternative — e.g. get_promises_tracker or get_mdb_vote for the underlying components — nor states when not to use it, leaving routing 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.