Skip to main content
Glama
Sign In
malkreide

lobbywatch-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

lobbywatch_get_transparenzquote

Read-onlyIdempotent

Aggregate compensation-disclosure transparency ratings for all parliamentarians or a selected commission and return the label distribution to compare transparency across groups.

Instructions

Aggregate the verguetungstransparenz_beurteilung values across all parliamentarians (or a commission subset) and return the distribution.

Useful to answer: 'How transparent is the education commission on compensation disclosure?'

Use cases: - "How transparent is the FK-N on compensation disclosure?" - "Distribution of transparency labels across the whole parliament" - "Compare WBK-N transparency vs the council average"

Input Schema

NameRequiredDescriptionDefault
kommissionNo

Output Schema

NameRequiredDescriptionDefault
scopeYes
staleNoSet only when the dump could not be refreshed and an older cached copy answered instead. The data may miss changes made since `stale.cached_at` — say so when relaying it.
totalYes
sourceNoData: Lobbywatch.ch — CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). Not an official register; community-researched records.
provenanceYesWhich endpoint / dump the payload came from
nach_bewertungNo
quote_ausreichendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.8
    • addedOutput schema / $defs
      Added value: +{
+  "StaleDump": {
+    "description": "The weekly dump could not be refreshed; an older cached copy answered.",
+    "properties": {
+      "age_seconds": {
+        "description": "Age of the answering copy",
+        "title": "Age Seconds",
+        "type": "integer"
+      },
+      "cached_at": {
+        "description": "When the answering copy was downloaded (UTC, ISO 8601)",
+        "title": "Cached At",
+        "type": "string"
+      },
+      "reason": {
+        "description": "Why the refresh failed",
+        "title": "Reason",
+        "type": "string"
+      }
+    },
+    "required": [
+      "cached_at",
+      "age_seconds",
+      "reason"
+    ],
+    "title": "StaleDump",
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / stale
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/StaleDump"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Set only when the dump could not be refreshed and an older cached copy answered instead. The data may miss changes made since `stale.cached_at` — say so when relaying it."
+}
  2. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it states what underlying field is aggregated and that omitting the commission defaults to the whole parliament. No permission or rate-limit detail is given, but none is needed for a local-dump read.

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?

The core operation is front-loaded in the first sentence and the example questions are tucked below it. The bulleted use cases partly restate the 'Useful to answer' line, so there is slight redundancy, but nothing is bloated for a tool of this complexity.

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?

An output schema exists, so the description needn't explain the return shape, and it correctly focuses on intent and scope. Combined with the annotations it gives an agent enough to invoke the tool correctly; only the commission-identifier format is left to inference.

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?

There is one parameter with 0% schema description coverage, so the description has to carry the load. It implies 'kommission' accepts a commission identifier and the examples (FK-N, WBK-N) hint at the accepted format, which is genuinely useful. However, it never states the format or matching rules explicitly and doesn't mention the maxLength constraint, so compensation is only partial.

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 gives a specific verb and resource: it aggregates verguetungstransparenz_beurteilung values and returns the distribution, with scope stated as 'all parliamentarians (or a commission subset)'. That is far more informative than the opaque German tool name. It does not, however, explicitly differentiate itself from siblings such as lobbywatch_get_ranking, so it stops short of a 5.

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?

Usage context is clear and concrete: 'Useful to answer: How transparent is the education commission...' plus three example questions covering whole-parliament, single-commission, and comparison scenarios. There is no explicit when-not guidance or named alternative (e.g. get_ranking), so it does not reach 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools