Skip to main content
Glama

transparent.ruhr

gremien

Read-only

Die aktuellen Gremien einer Körperschaft (Rat, Ausschüsse, Bezirksvertretungen, Fraktionen), ohne Mitglieder.

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

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changed
    • 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.6/5.0
Behavior3/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 needs no restating. The description adds a genuine content-scope disclosure with "ohne Mitglieder", warning that member data is not included, but says nothing about ordering, completeness, or response shape.

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?

One sentence, front-loaded with the resource and its scope, ending with the exclusion. Nothing is redundant or padded.

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 single-parameter read-only listing with full schema coverage, no output schema, and annotations covering safety, the description conveys what is returned and what is excluded. The only shortfall is that the shape of a Gremium entry is left unspecified.

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 kommune property already enumerates valid codes and points to the `kommunen` tool as the source. The description adds no additional meaning about the parameter, 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 states a specific resource (Gremien) with concrete subtypes (Rat, Ausschüsse, Bezirksvertretungen, Fraktionen) and an explicit scope qualifier ("aktuellen ... einer Körperschaft"). It does not name or contrast any sibling tool, so an agent must infer the boundary with kommunen and sitzungen.

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 required kommune parameter plus the resource name make it obvious this is the entry point for committee lists of a given municipality. There is no statement of when to prefer it over siblings or of follow-up patterns (e.g. using the result to query sitzungen).

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