switzerland-parliament-mcp-server

Chparl Search Members

chparl_search_members

Read-onlyIdempotent

Find current or former Swiss Parliament affiliation records by name, council, canton, party, or parliamentary group. membership defaults to current; former selects inactive records and all omits the activity filter. query matches a substring of a published first, last, or official name. Use each record’s personNumber with chparl_get_member for identity, full council terms, committees, and declared interests. Follow nextOffset with the same filters.

Input Schema

Name	Required	Description	Default
`limit`	No	Requested page size, default 20, effective maximum 100 with notice. Whole records may be fitted to the response byte budget.
`query`	No	Optional name substring, trimmed without changing internal punctuation or diacritics.
`offset`	No	Starting MemberCouncil record offset; continue with returned nextOffset.
`council`	No	N or S; exact German, French, and Italian council names are accepted. Resolve codes with chparl_list_reference topic councils.
`groupId`	No	Optional ParlGroupNumber from chparl_list_reference topic groups.
`partyId`	No	Optional Party identifier from chparl_list_reference topic parties.
`cantonId`	No	Optional Canton identifier from chparl_list_reference topic cantons.
`language`	No	Metadata language: de (default), fr, or it; uppercase is accepted.	de
`membership`	No	current (default), former, or all MemberCouncil records.	current

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Combined clamping, byte fitting, empty-result, or past-end guidance.
`hasMore`	No	Whether further matching affiliation records remain.
`members`	No	Complete MemberCouncil affiliation records delivered on this page.
`nextOffset`	No	Starting offset plus delivered records; absent when exhausted.
`provenance`	No	Attribution, publication status, and source download dates.
`totalCount`	No	Exact whole-query MemberCouncil record count when supplied upstream.
`returnedCount`	No	Number of complete MemberCouncil records delivered.
`effectiveLimit`	No	Effective requested page size after clamping.
`effectiveFilters`	No	Normalized search filters and resolved defaults.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world, so the safety profile is covered. The description adds genuinely non-structured behavior: default activity filtering and the requirement to reuse the same filters when following nextOffset. It does not mention the byte-budget truncation of results, which is only visible in the schema.

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?

Four sentences, each carrying distinct information: scope, filter semantics, query semantics, cross-tool routing, and pagination. Nothing is repeated from the schema verbatim and the core purpose is front-loaded.

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?

With nine optional parameters, full schema coverage, and an output schema, the description supplies what the structured fields cannot: filter-mode semantics, cross-tool routing, and pagination protocol. An agent can call and iterate this tool correctly from the description alone.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: the precise semantics of current/former/all activity filtering and the fact that query matches a substring of first, last, or official names rather than free text. Filter-to-reference-tool resolution is left to the schema.

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 ('Find ... Swiss Parliament affiliation records') plus the exact filterable dimensions (name, council, canton, party, parliamentary group). It also distinguishes itself from chparl_get_member by scoping this tool to search and routing detail lookups elsewhere.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains the membership modes ('current' default, 'former' selects inactive, 'all' omits the filter), how query substring matching works, and the handoff path: use personNumber with chparl_get_member for identity and terms. Pagination guidance ('Follow nextOffset with the same filters') closes the loop on repeated calls.

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

All switzerland-parliament-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.