Skip to main content
Glama
malkreide

lobbywatch-mcp

by malkreide

lobbywatch_search_parlamentarier_nach_branche

Read-onlyIdempotent

Search Swiss parliamentarians by industry or branch, using organization name or branche field, with optional commission filter to find specific interest group connections.

Instructions

Find parliamentarians with interessenbindungen matching a search term against the linked organisation's name, alias, and (when available) branche field. Optional commission filter.

Note: the Lobbywatch "essential" dump does not embed a branche taxonomy on each organisation — branche is referenced by id and resolved via the separate interessengruppe table. Version 0.1 therefore performs a substring match against organisation names and the branche field when present. Version 0.2 will add full cross-reference resolution.

Args: branche_query: Substring match (case-insensitive) against organisation.anzeige_name, organisation.name, organisation.branche (where present), e.g. "Verlag", "Pharma", "Bank", "Krankenkasse", "Bildung". kommission: Commission abbreviation to restrict the result to, e.g. "WBK-N" for the education commission of the National Council. limit: Max number of {parlamentarier, ib} pairs returned (1–200).

Use cases: - "Which WBK-N members hold mandates in the publishing industry?" - "Cross-filter Pharma × FK-N to surface health-policy lobbyists" - "List every parliamentarian with a 'Krankenkasse' connection"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branche_queryYes
kommissionNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
queryYes
countYes
trefferNoList of {parlamentarier, interessenbindung} pairs matching the branche
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds specific behavioral details such as substring matching, case-insensitivity, and version 0.1 limitations, which go beyond the annotations.

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?

Well-structured with purpose, limitations, Args, and Use cases. While informative, it could be slightly more concise; the version note and future improvements add length but are still relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description adequately covers input semantics, use cases, and behavioral nuances. No critical gaps remain for agent to use the tool correctly.

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

Parameters5/5

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

Schema has 0% description coverage, but the description fully explains all three parameters: branche_query (matching fields), kommission (commission abbreviation), and limit (range 1-200). It compensates completely for the missing schema descriptions.

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?

The description clearly states it finds parliamentarians based on a search term against organisation fields, with optional commission filter. It distinguishes from siblings like 'lobbywatch_get_parlamentarier' by focusing on industry/commission search.

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?

Provides clear use cases (e.g., 'Which WBK-N members hold mandates in publishing?') and explains limitations like substring matching. However, it does not explicitly mention when not to use or name alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/lobbywatch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server