Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Legislativer Fußabdruck

get_legislative_footprint
Read-onlyIdempotent

Zeigt den Legislative Footprint eines EU-Dossiers: WER hat die Berichterstatter zu diesem Gesetzgebungsverfahren getroffen. Berichterstatter, Schattenberichterstatter und Ausschussvorsitzende MÜSSEN ihre Treffen mit Interessenvertretern veröffentlichen — daraus ergibt sich, welche Verbände auf ein Verfahren eingewirkt haben und welche nicht. procedure='2023/0448(COD)' liefert alle Treffen zu einem Dossier, mep='Andresen' die Treffen einer Person, organisation='BDEW' oder tr_number die Treffen einer Organisation. Gibt Datum, Abgeordnete:n, Rolle, Ausschuss, Betreff und die beteiligten Organisationen mit Transparenzregister-Nummer zurück. WICHTIG für die Bewertung: Treffen, die von Mitarbeitenden im Auftrag geführt wurden, sind als solche gekennzeichnet — sie sind kein persönlicher Kontakt der/des Abgeordneten. Quelle: Europäisches Parlament, veröffentlichte Treffen (CC BY 4.0). 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

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_legislative_footprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
mepNoOptional: Name der/des Abgeordneten, z. B. 'Andresen' oder 'Rasmus Andresen'
limitNoAnzahl Ergebnisse, max. 50. Standard: 15
date_toNoOptional: Datum bis (ISO)
capacityNoOptional: Rolle — 'rapporteur', 'shadow.rapporteur', 'committee.chair', 'rapporteur.opinion', 'shadow.rapporteur.opinion', 'member'
date_fromNoOptional: Datum ab (ISO, z. B. '2025-01-01')
procedureNoVerfahrensnummer des Dossiers, z. B. '2023/0448(COD)'. Der wichtigste Filter — liefert den Footprint eines konkreten Gesetzgebungsverfahrens.
tr_numberNoOptional: Transparenzregister-Nummer der Organisation, z. B. '94038094048-01'. Findet nur Treffen, bei denen die Nummer auch deklariert wurde — Freitext-Angaben werden so NICHT gefunden.
organisationNoOptional: Name der Organisation, z. B. 'BDEW' oder 'Greenpeace' (Teiltreffer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context: official source with CC BY 4.0 licence, the caveat that meetings conducted by staff on behalf of an MEP are marked and are not personal contact, and the per-hit Beleg-ID that must be cited verbatim. That is substantive disclosure beyond the annotations.

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?

The key scoping statement is front-loaded, and the filter-by-filter breakdown is easy to scan. There is minor waste: the citation duty is stated twice (the '[[beleg:…]]' sentence and the closing sentence about Kennung and both links), and the bracketed '[Ohne KI: …]' line is promotional rather than operational.

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?

With 8 optional parameters and no output schema, the description supplies the return fields it would otherwise be missing (date, MEP, role, committee, subject, organisations with transparency-register number) plus the citation contract. Combined with 100% schema coverage and explicit annotations, an agent has everything needed to call and cite the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description raises it by explaining that 'tr_number' only matches explicitly declared numbers (free-text entries are missed) and that 'organisation' is a partial match, plus which filter is primary for a dossier-level footprint. It does not cover 'capacity', 'date_from', 'date_to' or 'limit' 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 a specific resource and verb: it shows the legislative footprint of an EU dossier, i.e. who met the rapporteurs, with explicit example filters ('procedure=2023/0448(COD)', 'mep=Andresen'). It is clear what the tool produces, but it never distinguishes itself from related siblings such as get_lobby_network, get_lobby_druck_index or get_eu_lobby_network, so the agent must infer the boundary.

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

Usage Guidelines4/5

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

It explains which filter answers which question ('procedure' gives the whole dossier footprint, 'mep' gives one person, 'organisation'/'tr_number' give one organisation) and flags 'procedure' as the most important filter. It also routes the agent to pruefe_belege for verifying the generated answer. It stops short of stating when not to use it or how it differs from the lobby-network siblings.

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.