Skip to main content
Glama

transparent.ruhr

drucksache

Read-only

Eine Drucksache von parlamente.org mit allen Dokumenten (bei Anfragen auch die Antwort), Urhebern und verwandten Drucksachen desselben Vorgangs.

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": {
      "parlament": "<parlament>",
      "nummer": "<nummer>"
    },
    "name": "drucksache"
  }
}

Input Schema

NameRequiredDescriptionDefault
nummerYesDrucksachennummer als "Wahlperiode/Nummer", z. B. "21/8318" (Feld `nummer` aus `drucksachen_suchen`).
parlamentYesParlament: bundestag, berlin, brandenburg, sachsen, nrw, hessen.

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."New value: +"Parlament: bundestag, berlin, brandenburg, sachsen, nrw, hessen."
  2. Changed2 schema fields changed
    • addedInput schema / properties / nummer / description
      Added value: +"Drucksachennummer als \"Wahlperiode/Nummer\", z. B. \"21/8318\" (Feld `nummer` aus `drucksachen_suchen`)."
    • addedInput schema / properties / parlament / description
      Added value: +"Parlament: bundestag, berlin, brandenburg, sachsen."
  3. First observed

TDQS

B3.2/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 safety is covered. The description adds genuine value by describing the payload envelope (all documents, answers for Anfragen, authors, related papers), but says nothing about behavior on an invalid parliament/number, empty results, or payload size.

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?

A single front-loaded sentence identifying the resource and its contents; the parenthetical about Anfragen answers is informative rather than padding. Slightly dense but no wasted sentences.

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?

With only two fully documented parameters, read-only annotations, and no output schema, the description's account of what the response contains is exactly the missing piece and it supplies it. Only failure/empty-result behavior is left unaddressed.

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 both parameters are documented in detail there, including the 'Wahlperiode/Nummer' format and the parliament list. The description contributes no additional parameter semantics, 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?

States a specific resource — a single Drucksache from parlamente.org — and enumerates what it bundles (documents, inquiry answers, Urheber, verwandte Drucksachen of the same Vorgang). This is far more than restating the name, though it never explicitly contrasts fetching one record with the sibling search tool drucksachen_suchen.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance in the description; the only routing hint (taking `nummer` from `drucksachen_suchen`) lives in the schema, not the description. An agent must infer that this is the single-record lookup counterpart to the search tool.

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