Skip to main content
Glama

ParliamentOS – Bundestag, Landtage, Nationalrat, EU

Lobbyregister suchen

search_lobby
Read-onlyIdempotent

Findet Lobbyorganisationen nach Thema in den nationalen Lobbyregistern (DE: Bundestag, laufend aktualisiert; AT: österreichisches Register) UND im EU-Transparenzregister, sofern die Organisation dort mit Sitz im gewählten Land eingetragen ist. Jeder Treffer weist sein Register aus; mit register='national' oder register='eu' lässt sich auf eine Quelle einschränken. Achtung: Budgetangaben sind zwischen den Registern nicht vergleichbar (national = gemeldete Jahresausgaben, EU = Obergrenze einer Selbstauskunfts-Spanne). Für EU-Lobbyarbeit mit Kommissionstreffen und EP-Zugangsausweisen ist search_eu_lobby das passende Werkzeug. 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

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": {
      "topic": "<topic>"
    },
    "name": "search_lobby"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAnzahl Ergebnisse. Standard: 5
topicYesThema, z. B. 'Energie', 'Pharma', 'Rüstung'
countryNoLand: 'DE' (Standard) oder 'AT' für Österreich
registerNoOptional: 'national' (nur DE- bzw. AT-Register) oder 'eu' (nur EU-Transparenzregister). Ohne Angabe: beide, jeweils mit Registerangabe pro Treffer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description rightly spends its words elsewhere: per-hit register attribution, the budget-comparability caveat (national = reported annual spend vs EU = upper bound of a self-disclosure range), the Beleg-ID citation contract, and verification via pruefe_belege. These are substantive behavioural traits an agent could not infer from 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.

Conciseness3/5

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

Purpose and the sibling exclusion are front-loaded, which is good, but the citation block is repetitive (Beleg-ID, Kennung, Beleg-Seite, Original, server instructions) and the bracketed "Ohne KI" tagline adds no actionable content. Several sentences restate the same citation requirement rather than adding new information.

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 four simple parameters, full schema coverage, and no output schema, the description covers what matters: what comes back (hits with register labels, Beleg-ID, Kennung and links), the cross-register comparability trap, and how results are verified downstream. Nothing an agent needs in order to call and cite this tool correctly is missing.

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 would be 3. The description goes beyond the schema by clarifying that the EU source only matches organisations seated in the chosen country, which changes how `country` interacts with the EU register, and by explaining what per-hit register labelling means for the `register` parameter.

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 specific verb and resource ("Findet Lobbyorganisationen nach Thema") plus the exact corpora searched (DE Bundestag, AT Register, EU-Transparenzregister under a seat condition). It explicitly distinguishes itself from search_eu_lobby, so an agent can separate 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?

Gives an explicit routing rule: for EU lobbying with Commission meetings and EP access badges, search_eu_lobby is the right tool, which is a clear when-not-to-use case. It also explains how register='national'/'eu' narrows sources, and the country-scoped EU inclusion rule leaves nothing to inference.

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.