Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Lobby-Druck-Index

get_lobby_druck_index
Read-onlyIdempotent

Lobby-Druck-Index je EU-Verfahren (Kennzahl A8): Ranking der Dossiers nach veröffentlichten Treffen von MdEP mit Verfahrensbezug — je Verfahren Treffen, beteiligte Abgeordnete, Organisationen, Treffen je MdEP sowie der Wirtschaftsanteil der im EU-Transparenzregister zugeordneten Organisationskontakte. Wahlweise Top-N-Ranking (limit, sortierung) oder Einzelabfrage per Verfahrensnummer (procedure). Reines Aggregat je Dossier, kein Personenbezug. Die Treffenliste eines Dossiers liefert get_legislative_footprint. Quellen: EP-Treffenregister und EP Open Data (CC BY 4.0), EU-Transparenzregister. Professional+ Tier. [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_lobby_druck_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Dossiers im Ranking, max. 50. Standard: 20
procedureNoOptional: Verfahrensnummer, z. B. '2022/0051(COD)' — liefert nur dieses Dossier
mindestensNoOptional: nur Dossiers mit mindestens so vielen Treffen. Standard: 10
sortierungNo'treffen' (Standard), 'je_mdep' (Treffen je MdEP) oder 'wirtschaft' (Wirtschaftsanteil der zugeordneten Kontakte)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the bar is lower, yet the description adds real context: it is a pure per-dossier aggregate with no personal data, and it discloses data provenance (EP meeting register, EP Open Data CC BY 4.0, EU Transparency Register) plus a Professional+ tier gate. It does not discuss refresh cadence or how recently published meetings enter the index, which is the main remaining behavioral gap.

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 definition is front-loaded with the metric and the mode choice before sources and tier, and nearly every clause carries information. The trailing '[Ohne KI: ...]' disclaimer and the licence/tier tail are somewhat boilerplate and dilute the core signal.

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 no output schema, the description compensates by enumerating the returned figures per dossier and clarifying the aggregation granularity, which is what an agent needs to decide whether this tool answers the question. Sources, licence and access tier round out everything needed to call it 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 baseline is 3; the description earns an extra point by explaining the interaction between parameters — that limit and sortierung select ranking mode while procedure switches to a single-dossier lookup. It does not mention the 'mindestens' minimum-meetings filter, leaving that entirely to the schema.

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?

Names a concrete computed metric (Lobby-Druck-Index, Kennzahl A8) per EU procedure and enumerates exactly what it aggregates: meetings, MEPs involved, organisations, meetings per MEP, and the business share of transparency-register contacts. It also explicitly contrasts itself with get_legislative_footprint, which returns the raw meeting list, so an agent can distinguish the two without opening either schema.

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?

States the two operating modes up front — Top-N ranking via limit/sortierung or a single lookup via procedure number — and names the alternative tool for the underlying meeting data. The only minor omission is an explicit 'when not to use', but the sibling routing plus the Professional+ tier note covers the practical decision.

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.

Resources