Skip to main content
Glama

transparent.ruhr

vorlage

Read-only

Einzelheiten zu einer Vorlage: Titel, Art, Datum, federführendes Gremium, maschinelle Zusammenfassung, amtliches Dokument, Beratungsfolge mit Ergebnissen und, bei Anfragen, die Antwort der Verwaltung (bzw. umgekehrt).

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": {
      "kommune": "<kommune>",
      "id": "<id>"
    },
    "name": "vorlage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID der Vorlage: das Feld `id` aus `vorlagen_suchen` bzw. die Zahl am Ende der Vorlagen-URL (…/papers/88476). Nicht das Aktenzeichen.
kommuneYesKürzel der Körperschaft aus `kommunen`: bochum, essen, hamm, gladbeck, castrop-rauxel, kreis-recklinghausen, moers, hamminkeln, neukirchen-vluyn, sprockhoevel, rvr.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"ID der Vorlage: das Feld `id` aus `vorlagen_suchen` bzw. die Zahl am Ende der Vorlagen-URL (…/papers/88476). Nicht das Aktenzeichen."
    • addedInput schema / properties / kommune / description
      Added value: +"Kürzel der Körperschaft aus `kommunen`: bochum, essen, hamm, gladbeck, castrop-rauxel, kreis-recklinghausen, moers, hamminkeln, neukirchen-vluyn, sprockhoevel, rvr."
  2. First observed

TDQS

A3.7/5.0
Behavior4/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 goes beyond that by disclosing the returned payload structure — Beratungsfolge mit Ergebnissen, amtliches Dokument, maschinelle Zusammenfassung — and the conditional case that inquiries return the administration's answer (bzw. umgekehrt), which is genuinely useful shape information given there is no output schema. Minor gap: nothing about behaviour for an unknown or mismatched id.

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 sentence, front-loaded with the purpose, followed by a compact enumeration of fields. Every listed item carries information; the only slight cost is the parenthetical clause at the end, which is still meaningful for the inquiry case.

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, no nested objects and no output schema, the description's enumeration of return content is what an agent needs to decide to call it. The one missing piece is the conceptual boundary to the sibling drucksache.

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, including the warning that id is not the Aktenzeichen and the enumeration of valid kommune codes. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description names a specific verb+resource ("Einzelheiten zu einer Vorlage") and enumerates the exact content returned: Titel, Art, Datum, federführendes Gremium, Zusammenfassung, amtliches Dokument, Beratungsfolge. An agent can tell it is the single-record detail lookup. It does not, however, distinguish Vorlage from the sibling drucksache, which is the closest conceptual neighbour.

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?

Usage is only implied: the pair name vorlagen_suchen plus the schema note that id comes from that tool signal the list→detail workflow. There is no explicit statement of when to use this versus drucksache, nor any prerequisite or exclusion, so the agent must infer the routing.

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