Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Weg eines Wahlversprechens

get_promise_journey
Read-onlyIdempotent

PromiseToLaw™ — Verfolgt den Weg eines Wahlversprechens durch den Bundestag: Welche Partei hat was versprochen? Gab es eine Abstimmung? Welches Gesetzgebungsverfahren ist entstanden? Hat die Partei ihr Versprechen gehalten? Ideal für Transparenz-Journalismus und politische Analyse. Jeder Treffer nennt am Ende der Antwort Kennung, Beleg-Seite und Original; zitiere mit Kennung und beiden Links wie in der Server-Anleitung. [🤖 KI-Einsatz (EXTRAHIERT, Claude Haiku 4.5 + Claude Sonnet 4.6): Versprechenstexte und Status sind maschinell aus den Wahlprogrammen gewonnen.]

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": {
      "query": "<query>"
    },
    "name": "get_promise_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Versprechen, max. 5. Standard: 3
partyNoOptional: Partei filtern, z. B. 'SPD', 'Grüne', 'CDU'
queryYesSuchwort oder Thema, z. B. 'Mindestlohn', 'CO2-Preis', 'Mietpreisbremse'
wahlperiodeNoOptional, nur zusammen mit party: 21 (Standard) = Wahlprogramm zur Bundestagswahl 2025, 20 = Wahlprogramm zur Bundestagswahl 2021. Mit party bezieht sich jede Antwort auf genau ein Programm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds real value beyond them: it discloses that the promise texts and status are machine-extracted from party programs by named models, which flags data-reliability caveats. It also states that each result carries an identifier, evidence page and original source and mandates citation, which the annotations say nothing about. Only the response shape/pagination remains undisclosed.

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-loads the resource then a chain of question fragments that efficiently convey the journey being traced; the citation and AI-provenance sentences are load-bearing rather than padding. The trademark label and the trailing bracketed model attribution are somewhat noisy but do not obscure the core.

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 4-parameter search tool with no output schema, the description adequately covers what it returns (identifier, evidence page, original, citation requirements) and warns that the underlying data is machine-extracted. It lacks only routing against the near-identical sibling tracker.

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 the schema already documents query, party, wahlperiode and limit including the max-5 default. The description adds only indirect hints (the party/versprechen framing and that each response with party refers to exactly one program), which largely restates the wahlperiode note in the schema. Baseline 3 is appropriate.

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?

States a concrete verb+resource: tracing a campaign promise ('Weg eines Wahlversprechens') through the Bundestag, and enumerates the sub-questions it answers (party promise, vote, legislative procedure, kept-or-broken). It never distinguishes itself from the similarly named sibling get_promises_tracker, so an agent cannot tell from the description which one to pick.

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?

Gives a use case ('Ideal für Transparenz-Journalismus und politische Analyse'), which implies context, but offers no when-not guidance and no explicit alternative. Nothing tells the agent how this differs from get_promises_tracker or get_legislative_footprint.

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.