Skip to main content
Glama

transparent.ruhr

sitzungen

Read-only

Sitzungen von Rat, Ausschüssen und Bezirksvertretungen in einem Zeitraum. Ohne Datumsangaben die nächsten 30 Tage. Die Tagesordnung liefert sitzung.

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>"
    },
    "name": "sitzungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
bisNoLetzter Tag, JJJJ-MM-TT; leer = 30 Tage nach `von`.
vonNoErster Tag, JJJJ-MM-TT; leer = heute.
anzahlNoHöchstzahl der Treffer, 1 bis 100.
gremiumNoWortanfang im Gremiennamen, z. B. "Rat", "Mobilität" oder "Bezirksvertretung Mitte". "Rat" findet den Rat, nicht "Integrationsrat" oder "Beirat". Leer = alle Gremien.
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. Changed5 schema fields changed
    • addedInput schema / properties / anzahl / description
      Added value: +"Höchstzahl der Treffer, 1 bis 100."
    • addedInput schema / properties / bis / description
      Added value: +"Letzter Tag, JJJJ-MM-TT; leer = 30 Tage nach `von`."
    • addedInput schema / properties / gremium / description
      Added value: +"Wortanfang im Gremiennamen, z. B. \"Rat\", \"Mobilität\" oder \"Bezirksvertretung Mitte\". \"Rat\" findet den Rat, nicht \"Integrationsrat\" oder \"Beirat\". Leer = alle Gremien."
    • 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."
    • addedInput schema / properties / von / description
      Added value: +"Erster Tag, JJJJ-MM-TT; leer = heute."
  2. First observed

TDQS

A4/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. Beyond that, the description discloses the non-obvious default window of 30 days when no dates are passed and clarifies that agenda items are not part of this result — both genuine behavioral facts. Pagination/ordering behavior is left unstated, though `anzahl` in the schema partly covers volume.

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, front-loaded with what the tool returns, then the default behavior, then the sibling hand-off. No filler and nothing redundant for an agent to skip over.

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?

For a five-parameter, read-only listing tool with fully documented schema, the description covers scope, default window, and the boundary with the detail tool. Since no output schema exists, one more line on the shape of the returned list (and whether results are capped by `anzahl`) would close the remaining gap.

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 coverage is 100%, and the parameter descriptions are rich (including the prefix-matching rule for `gremium` and the kommune short-code list). The description adds no parameter meaning beyond the schema; its date statement restates the `von`/`bis` defaults already documented. 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 (Sitzungen von Rat, Ausschüssen und Bezirksvertretungen) and the scoping dimension (Zeitraum), and explicitly separates it from the sibling `sitzung`, which supplies the Tagesordnung. Lacks an explicit verb such as "listet", but an agent can still tell what the tool returns and how it differs from the detail tool.

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?

Gives a clear default rule (no dates = next 30 days) and an explicit alternative for a related need (agenda details via `sitzung`). It does not say when to prefer this over `gremien` or the `*_suchen` siblings, so the routing is clear only for the one alternative it names.

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