Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Latenz Brüssel-Berlin

get_bruessel_berlin_latenz
Read-onlyIdempotent

Brüssel-Berlin-Latenz (Kennzahl A5 aus docs/normos/odbl-kennzahlen-kandidaten.md): Tage von der Annahme eines Kommissionsdokuments (Datum aus EUR-Lex/CELLAR, dem EU-Publikationsamt) bis zur Zuleitung der EU-Vorlage an Bundestag und Bundesrat (DIP), je Wahlperiode und Dokumentart (Vorschlag oder Mitteilung/Bericht): Median, Quartile, Spanne. Je Dokumentart dazu die Fälle an Minimum, Median und Maximum mit zwei Kennungen [[beleg:eu-kom:…]] (Datum der Annahme durch die Kommission) und [[beleg:bt-vpos:…]] (Datum der Zuleitung), prüfbar mit pruefe_belege (Zitat-Vertrag v6). Anzahl, Median, Quartile und Spanne je Zeile tragen die Kennung [[beleg:kennzahl:…]] (Zitat-Vertrag v7): Sie steht für die festgeschriebene Eingangsliste dieser Zeile, aus der pruefe_belege die Zahlen nachrechnet. Zusätzlich der Abstand zwischen dieser Zuleitung und der Ausschussbefassung im Europäischen Parlament je Verfahrenstyp (negativ = Berlin zuerst). Kein Personenbezug. Belastbar derzeit nur für WP 21 (Vorgangspositionen). In die Latenz gehen nur Vorlagen mit KOM- oder JOIN-Nummer und Kommissionsdatum ein; die Abdeckung steht in der Antwort: Zuleitungen je Gruppe, bei jedem Aufruf aus dem Bestand gezählt, jede Anzahl mit Kennung [[beleg:kennzahl:…]], aus deren festgeschriebener Liste pruefe_belege nachzählt. Quellen: DIP, EUR-Lex/CELLAR, EP Open Data (CC BY 4.0). Professional+ Tier. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_bruessel_berlin_latenz"
  }
}

Input Schema

NameRequiredDescriptionDefault
wahlperiodeNoWahlperiode des Bundestages, 20 oder 21. Standard: 21
verfahrenstypNoOptional: OEIL-Verfahrenstyp, z. B. 'COD' (ordentliches Gesetzgebungsverfahren), 'NLE', 'BUD', 'CNS', 'APP'. Ohne Angabe alle Typen plus Gesamtzeile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 profile is covered. The description adds meaningful context beyond that: sources (DIP, EUR-Lex/CELLAR, EP Open Data, CC BY 4.0), a 'Professional+ Tier' access requirement, the no-personal-data property, per-call coverage counts recomputed from the corpus, and the citation obligation at the end of each answer. The reliability caveat for WP 21 and the negative-value convention for EP committee timing are genuinely useful behavioral disclosures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The metric definition is front-loaded correctly, but the text is a dense run-on with nested parentheses that is substantially longer than needed. The [[beleg:kennzahl:…]] identifier contract and the pruefe_belege recomputation rule are explained twice in near-identical terms, and the closing citation instructions repeat the same requirement again, so several sentences do not earn their place.

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 carries the burden of describing returns, and it does: per-row count, median, quartiles and range, plus min/median/max exemplar cases with two identifiers per document type, coverage counts, and the EP-committee lag. Inclusion rules and the WP 21 reliability limit round it out. Only the precise shape of the response rows remains underspecified.

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% for both parameters, so the baseline is 3. The description reinforces that results are cut 'je Wahlperiode' and 'je Verfahrenstyp' and explains what the Verfahrenstyp comparison means (negative = Berlin first), but it adds no format or validity detail beyond what the schema already states.

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 description names the exact computation: days from Commission adoption of a document (EUR-Lex/CELLAR) to transmission to Bundestag/Bundesrat (DIP), broken down by Wahlperiode and document type, with median, quartiles and range. That is a specific verb-plus-resource statement an agent can match to a request. It does not explicitly differentiate itself from sibling metrics such as get_bundestag_verfahrenskennzahlen, so it falls short of a 5.

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?

Useful constraints are stated: 'Belastbar derzeit nur für WP 21 (Vorgangspositionen)' and the inclusion rule that only documents with a KOM/JOIN number and Commission date count. It also points to pruefe_belege for verification, but that is a companion for citation checking rather than a routing alternative. There is no explicit statement of when to choose this metric over a sibling metric, so guidance is implied rather than prescriptive.

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.