lobbywatch-mcp

Overview Schema Source Related Servers Discussions Admin

lobbywatch_list_interessenbindungen

Read-onlyIdempotent

Retrieve a Swiss parliamentarian's declared conflicts of interest and mandates by name or ID, with filters for active or full-time roles.

Instructions

Return the list of interessenbindungen (conflicts of interest) for one parliamentarian, optionally restricted to full-time or currently-active mandates.

On a fuzzy miss, near-miss candidates are returned in suggestions (audit ARCH-003).

Args: name_or_id: ID or name (fuzzy). nur_hauptberuflich: If True, only main-occupation mandates. nur_aktiv: If True, drop mandates with an end date (bis) set.

Use cases: - "Which active mandates does Jositsch hold today?" - "List Anna Mustermann's full-time mandates only" - "Give me every IB ever declared by parliamentarian #1"

Input Schema

Name	Required	Description	Default
`nur_aktiv`	No
`name_or_id`	Yes
`nur_hauptberuflich`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`stale`	No	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.
`source`	No		Data: Lobbywatch.ch — CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). Not an official register; community-researched records.
`provenance`	Yes	Which endpoint / dump the payload came from
`suggestions`	No	Near-miss fuzzy candidates when the lookup failed (ARCH-003)
`parlamentarier_id`	Yes
`interessenbindungen`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.8Oct 15, 2026

addedOutput schema / $defs / StaleDump

Added value: +{
+  "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."
+}

First observedv0.3.1Jun 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-open-world semantics, so the safety profile is covered. The description adds genuine behavioral context beyond that: fuzzy-name misses return near-miss candidates in a 'suggestions' field (audit ARCH-003), and nur_aktiv drops mandates with an end date set. It does not mention rate limits or result ordering, but for a read-only list tool this is solid.

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?

Purpose and the fuzzy-miss caveat are front-loaded, then args, then use cases. Every section earns its place, though the use-case block repeats filter semantics already stated in Args, adding mild redundancy.

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 return values need not be explained, and the description covers the mutation-free behavior, the three parameters and the fuzzy-match edge case. Missing only the default of nur_aktiv and any note on result scope/ordering for a complete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does: name_or_id is 'ID or name (fuzzy)', nur_hauptberuflich means only main-occupation mandates, nur_aktiv drops mandates with an end date set. The one gap is not noting that nur_aktiv defaults to true in the schema, which could surprise an agent expecting all mandates.

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?

States a specific verb and resource ('Return the list of interessenbindungen'), glosses the German term as conflicts of interest, and scopes it to 'one parliamentarian' with optional filters. This is clearly distinguishable from siblings like get_parlamentarier or get_lobbygruppe without opening any schema.

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?

Three concrete use cases ('Which active mandates does Jositsch hold today?', 'full-time mandates only', 'every IB ever declared by #1') make the intended usage unambiguous and show how the filter flags combine. It stops short of naming an alternative tool or stating when not to use it, so it misses the top tier.

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

Deploy Server