Skip to main content
Glama

transparent.ruhr

sitzung

Read-only

Eine Sitzung mit ihrer öffentlichen Tagesordnung: Tagesordnungspunkte, zugehörige Vorlagen und, soweit die Quelle sie liefert, Ergebnisse. Nichtöffentliche Punkte sind nicht enthalten.

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": "sitzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID der Sitzung: das Feld `id` aus `sitzungen` bzw. die Zahl am Ende der Sitzungs-URL (…/meetings/12345).
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 Sitzung: das Feld `id` aus `sitzungen` bzw. die Zahl am Ende der Sitzungs-URL (…/meetings/12345)."
    • 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 adds genuine behavioral context by stating the content scope and the important filtering rule that nichtöffentliche Punkte are excluded. It does not cover error behavior for an unknown id or how complete the Ergebnisse are when the source omits them, which keeps it below a 5.

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?

Three short lines, front-loaded with the resource and then the payload, with no filler. It is efficient, though the missing verb and the lack of a routing sentence make it slightly less actionable than it could be at the same length.

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 and no output schema, the description carries the burden of describing the return value, and it does so adequately by listing Tagesordnung, Vorlagen and Ergebnisse plus the non-public exclusion. What is missing is edge-case behavior (nonexistent id, kommunen mismatch), which is a modest gap for a simple read tool.

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 the schema already explains `id` (field from `sitzungen` or trailing number of the meeting URL) and `kommune` (Kürzel list). The description adds nothing about either parameter, 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?

The description identifies the resource precisely (a single Sitzung) and enumerates its payload: public Tagesordnung, Tagesordnungspunkte, zugehörige Vorlagen and, where available, Ergebnisse. The singular form plus the detail-oriented payload implicitly contrasts with the list tool `sitzungen`, but no sibling is named explicitly, so the differentiation is left to inference.

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: an agent can deduce this is the detail lookup to call after `sitzungen`, but the description never says when to use it versus `sitzungen`, `vorlage` or `drucksache`. There are no prerequisites, no exclusions beyond the non-public filter, and no routing guidance.

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