Skip to main content
Glama

Ratssitzungen am Ort

ratssitzungen
Read-onlyIdempotent

Öffentliche Sitzungen des Gemeinderats und seiner Ausschüsse für eine Postleitzahl in einem Zeitraum (Standard: ab heute 30 Tage, höchstens 92), mit den öffentlichen Tagesordnungspunkten und dem Link ins Ratsinformationssystem. Nur aus Kommunen, deren Ratsinformationssystem eine offene Lizenz nennt (bisher Dresden und Leipzig); sonst eine leere Liste mit Hinweis.

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": {
      "plz": "<plz>"
    },
    "name": "ratssitzungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
bisNoLetzter Tag im Format JJJJ-MM-TT
plzYesDeutsche Postleitzahl mit fünf Ziffern, z. B. „10117“
vonNoErster Tag im Format JJJJ-MM-TT (Standard: heute)
suchbegriffNoStichwort in Gremium oder Tagesordnung, z. B. „Haushalt“

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so safety is covered; the description adds the substantive behavior the annotations cannot express: the default and maximum time window, the hard coverage restriction, and the empty-list-with-note failure mode. It does not say what happens when a caller exceeds the 92-day cap (error vs. clamp), which is the remaining behavioral unknown.

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?

Two sentences, fully front-loaded: resource and scope first, then the caveat about licensing coverage and fallback behavior. No redundant restatement of the schema and no 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?

With no output schema, the description carries the return-value burden and discharges it by naming the public agenda items and the link into the Ratsinformationssystem. It is complete enough to decide whether to call it, though it omits any hint about response shape or handling of out-of-range date spans.

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%, so plz, von, bis and suchbegriff are already documented in the schema, which sets the baseline at 3. The description does add one thing the schema lacks: the 30-day default for the end of the range and the 92-day maximum span, which meaningfully constrains how bis should be set.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and scope: public sessions of the municipal council and its committees, keyed by postal code over a date range. The municipal/local-politics framing separates it cleanly from the national-level siblings (abgeordnete, abstimmungen, gesetze_suchen) without needing to name them.

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 real usage context: default window is 30 days from today, cap is 92 days, and the costly caveat that only municipalities with an open-license Ratsinformationssystem are covered (so far Dresden and Leipzig), otherwise an empty list plus a note. It stops short of pointing at an alternative tool when the locality is not covered, but the coverage caveat preempts the main misuse.

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