Skip to main content
Glama

transparent.ruhr

drucksachen_suchen

Read-only

Drucksachen von Bundestag und Landtagen (parlamente.org), parlamentsübergreifend, neueste zuerst. Beispiel: alle Kleinen Anfragen einer Fraktion.

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": "drucksachen_suchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
artNoDrucksachenart, z. B. "Kleine Anfrage", "Große Anfrage", "Antrag", "Gesetzentwurf", "Beschlussempfehlung". Muss genau passen.
seitNoNur Drucksachen ab diesem Tag, JJJJ-MM-TT.
anzahlNoHöchstzahl der Treffer, 1 bis 50.
fraktionNoEinbringende Fraktion als einheitliches Kürzel: AfD, BSW, CDU, CDU/CSU, CSU, Die Linke, FDP, Freie Wähler, fraktionslos, Grüne, PDS, SPD, SSW. Gezählt wird die einbringende Fraktion, nicht die antwortende Regierung.
parlamentNoParlament: bundestag, berlin, brandenburg, sachsen, nrw, hessen; leer = alle.
suchbegriffNoWörter oder Wortanfänge im Titel, alle müssen vorkommen ("Windkraft" findet auch "Windkraftanlagen"). Leer = ohne Titelfilter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / parlament / description
      Previous value: -"Parlament: bundestag, berlin, brandenburg, sachsen; leer = alle."New value: +"Parlament: bundestag, berlin, brandenburg, sachsen, nrw, hessen; leer = alle."
  2. Changed6 schema fields changed
    • addedInput schema / properties / anzahl / description
      Added value: +"Höchstzahl der Treffer, 1 bis 50."
    • addedInput schema / properties / art / description
      Added value: +"Drucksachenart, z. B. \"Kleine Anfrage\", \"Große Anfrage\", \"Antrag\", \"Gesetzentwurf\", \"Beschlussempfehlung\". Muss genau passen."
    • addedInput schema / properties / fraktion / description
      Added value: +"Einbringende Fraktion als einheitliches Kürzel: AfD, BSW, CDU, CDU/CSU, CSU, Die Linke, FDP, Freie Wähler, fraktionslos, Grüne, PDS, SPD, SSW. Gezählt wird die einbringende Fraktion, nicht die antwortende Regierung."
    • addedInput schema / properties / parlament / description
      Added value: +"Parlament: bundestag, berlin, brandenburg, sachsen; leer = alle."
    • addedInput schema / properties / seit / description
      Added value: +"Nur Drucksachen ab diesem Tag, JJJJ-MM-TT."
    • addedInput schema / properties / suchbegriff / description
      Added value: +"Wörter oder Wortanfänge im Titel, alle müssen vorkommen (\"Windkraft\" findet auch \"Windkraftanlagen\"). Leer = ohne Titelfilter."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious ordering behavior ('neueste zuerst') and cross-parliament scope, but says nothing about what a result record contains, how truncation at anzahl behaves, or whether matches are exact versus ranked.

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?

Two compact lines with the resource and ordering front-loaded and no filler; the example earns its place by demonstrating a parameter combination. Slight terseness leaves the tool's action implicit rather than explicit.

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

Completeness3/5

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

For a 6-parameter discovery tool with no output schema, the description should say something about what a Drucksache result looks like (title, date, faction, document link) and how the anzahl cap affects results. Annotations and a fully documented schema carry most of the burden, but the return-shape gap keeps this at a minimum-viable level.

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% and each parameter is documented in detail, including the exact-match requirement for art and the standardized fraktion abbreviations. The description's example loosely links art+fraktion, adding marginal meaning beyond the schema, so the baseline 3 applies.

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?

Names the concrete resource (Drucksachen von Bundestag und Landtagen via parlamente.org) and its scope (parlamentsübergreifend, neueste zuerst). The verb is only implied by the tool name rather than stated, and it does not explicitly distinguish itself from the sibling 'drucksache' (singular) or 'vorlagen_suchen', 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?

The example 'alle Kleinen Anfragen einer Fraktion' implicitly shows how to combine the art and fraktion parameters, which is useful guidance. However, there is no statement of when to prefer this over siblings like drucksache or vorlagen_suchen, and no mention of exclusions or prerequisites.

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