Skip to main content
Glama

transparent.ruhr

vorlagen_suchen

Read-only

Volltextsuche in Vorlagen, Anträgen, Anfragen und Mitteilungen der Räte im Ruhrgebiet (Titel und Dokumenttext).

Das Datum ist bei vielen Kommunen das der ersten Sitzung, nicht der Einreichung.
Einzelheiten und Beratungsergebnisse liefert `vorlage`.

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": {
      "suchbegriff": "<suchbegriff>"
    },
    "name": "vorlagen_suchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
artNoVorlagenart, wie die Quelle sie nennt, z. B. "Anfrage", "Antrag", "Beschlussvorlage der Verwaltung", "Mitteilung der Verwaltung". Muss genau passen; leer = alle Arten.
jahrNoNur Vorlagen dieses Jahres, z. B. 2026.
anzahlNoHöchstzahl der Treffer, 1 bis 30.
kommuneNoKürzel der Körperschaft aus `kommunen`, z. B. "bochum"; leer = alle Körperschaften.
suchbegriffYesSuchwörter für Titel und Dokumenttext, z. B. "Hitzeschutz" oder "Radweg Castroper Straße".
neueste_zuerstNotrue = nach Datum absteigend statt nach Relevanz sortieren.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / anzahl / description
      Added value: +"Höchstzahl der Treffer, 1 bis 30."
    • addedInput schema / properties / art / description
      Added value: +"Vorlagenart, wie die Quelle sie nennt, z. B. \"Anfrage\", \"Antrag\", \"Beschlussvorlage der Verwaltung\", \"Mitteilung der Verwaltung\". Muss genau passen; leer = alle Arten."
    • addedInput schema / properties / jahr / description
      Added value: +"Nur Vorlagen dieses Jahres, z. B. 2026."
    • addedInput schema / properties / kommune / description
      Added value: +"Kürzel der Körperschaft aus `kommunen`, z. B. \"bochum\"; leer = alle Körperschaften."
    • addedInput schema / properties / neueste_zuerst / description
      Added value: +"true = nach Datum absteigend statt nach Relevanz sortieren."
    • addedInput schema / properties / suchbegriff / description
      Added value: +"Suchwörter für Titel und Dokumenttext, z. B. \"Hitzeschutz\" oder \"Radweg Castroper Straße\"."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact: the stored date is usually the first-session date rather than the submission date, which changes how results should be interpreted. It does not mention result ordering defaults or truncation behavior, but `anzahl` and `neueste_zuerst` in the schema cover much of that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences: what is searched, the date caveat, and the escalation path. The purpose is front-loaded and no sentence is filler.

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?

There is no output schema, yet the description implies hits are summary-level and defers full content and results to `vorlage`, which is enough to set expectations. What a hit actually contains (title, date, link, snippet) is left implicit, a minor gap for a six-parameter search tool.

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 description coverage is 100%, so the baseline is 3; the description earns a point because the date caveat directly reinterprets the semantics of `jahr` and `neueste_zuerst` (sorting/filtering by session date, not submission date). It adds nothing about `art` matching rules or `kommune` codes, which the schema already handles.

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?

"Volltextsuche in Vorlagen, Anträgen, Anfragen und Mitteilungen der Räte im Ruhrgebiet (Titel und Dokumenttext)" gives a specific verb plus resource and even names the searched fields. It clearly separates itself from `vorlage` (detail view), but never explains how it differs from the sibling `drucksachen_suchen`, which an agent must guess.

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

Usage Guidelines4/5

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

The closing sentence explicitly routes the agent to `vorlage` when details or Beratungsergebnisse are needed, which is a real when-to-use-else rule. It lacks an explicit when-not condition against `drucksachen_suchen` and gives no guidance on choosing filters such as `art` versus free-text search.

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