ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Beleg nachschlagen

get_beleg

Read-onlyIdempotent

Öffnet einen Beleg anhand seiner Beleg-ID, z. B. [[beleg:at-rede:salzburg_17_4_1_207]], und gibt den Volltext mit Parlament, Datum, Redner/in, Rolle (Sitzungsleitung oder Fraktion), Sitzung und amtlicher Fundstelle zurück. Für Redebelege aus Bundestag (bt-rede), Nationalrat und Salzburger Landtag (at-rede), weiteren Landtagen (lt-rede), Berliner Abgeordnetenhaus (be-rede) und EU-Parlament (eu-rede); ebenso für alle übrigen Kennungen aus den Antworten der Werkzeuge, etwa Drucksachen (ds), Abstimmungen (bt-stimme, ep-stimme, ep-abst), Gesamtergebnisse namentlicher Abstimmungen im Bundestag (bt-abst, mit Ja, Nein, Enthaltung, nicht abgegebenen Stimmen und den Zahlen je Fraktion in der Zählung von abgeordnetenwatch.de), Lobbyregister (lobby-de, lobby-eu, lobby-at) und Treffen (ep-treffen). Nutze es, wenn jemand einen Beleg aus einer früheren Antwort sehen oder prüfen will. Lange Texte kommen in Abschnitten; die Antwort nennt den nächsten Wert für ab_zeichen. 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": {
      "beleg": "<beleg>"
    },
    "name": "get_beleg"
  }
}

Input Schema

Name	Required	Description
`beleg`	Yes	Beleg-ID wie in der Antwort, z. B. '[[beleg:at-rede:salzburg_17_4_1_207]]' oder 'at-rede:salzburg_17_4_1_207'
`ab_zeichen`	No	Optional: Textabschnitt ab diesem Zeichen (0 = Anfang). Standard: Anfang bzw. kurz vor der Belegspanne @von-bis
`max_zeichen`	No	Optional: Länge des Abschnitts, max. 20000. Standard: 8000

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is free. The description still adds real behavioral context beyond them: long texts arrive in chunks, the response names the next ab_zeichen value, and every hit ends with Kennung, Beleg-Seite and Original plus a citation obligation. It does not state rate limits or what happens with an invalid/expired ID, so it is good but not exhaustive.

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?

Purpose and return shape are front-loaded in the first sentence, and the pagination and citation instructions follow in a logical order. The long inline enumeration of ID prefixes is dense but each entry is load-bearing for input validity; only the 'Ohne KI' bracket at the end feels like boilerplate rather than tool guidance.

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

Completeness5/5

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

For a read-only fetch-by-ID tool with no output schema, the description covers what is returned, how chunking works, how to continue, and how to cite results. Nothing an agent needs in order to call it correctly and use the response is missing.

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% and all three parameters carry descriptions including defaults, so the schema already does the heavy lifting (baseline 3). The description adds one genuinely useful link: the response tells you the next value for ab_zeichen, which explains the continuation loop the parameter exists for. It gives no meaning for max_zeichen beyond what the schema states.

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 concrete verb and resource ('Öffnet einen Beleg anhand seiner Beleg-ID') and then enumerates exactly what the returned full text contains (Parlament, Datum, Redner/in, Rolle, Sitzung, amtliche Fundstelle). The parenthetical catalogue of supported ID namespaces (bt-rede, at-rede, lt-rede, be-rede, eu-rede, ds, bt-stimme, ep-abst, lobby-*, ep-treffen) makes the scope unmistakable and distinguishes it from every sibling, which are analytic endpoints rather than ID resolvers.

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

Usage Guidelines5/5

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

'Nutze es, wenn jemand einen Beleg aus einer früheren Antwort sehen oder prüfen will' gives an explicit trigger condition, and the ID-namespace list tells the agent precisely which values from prior tool responses are valid inputs. No sibling tool competes for this purpose, so a when-not clause is unnecessary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ParliamentOS – Bundestag, Landtage, Nationalrat, EU tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.