Skip to main content
Glama

switzerland-parliament-mcp-server

Chparl Search Business

chparl_search_business
Read-onlyIdempotent

Search Swiss parliamentary business by title substring, published submitter label, type, current status, submission session, inclusive submission dates, committee role, a member's own roles (personNumber, optionally one role such as author or cosignatory), or topic tag (tagId; without committeeId or personNumber it needs a submission-date window of at most 366 days). Use chparl_list_reference to resolve codes and chparl_get_business to read a returned businessId. Follow nextCursor with unchanged filters; newest canonical business IDs appear first. Author searches omit the business total. Committee searches, and personNumber searches without role, page role candidates and may return short pages without a distinct business total; a personNumber search with one role reports an exact total. Metadata labels remain in de, fr, or it without translation fallback.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chparl_search_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoWith personNumber only: one role the member holds. author (Urheber/Auteur/Autore), cosignatory (Mitunterzeichner/Cosignataire/Cofirmatario), spokesperson (Sprecher/Porte-parole/Relatore, e.g. for a parliamentary group's business), opponent (Bekämpfer/Opposant/Opposto), or successor (Übernehmer/Repreneur/Assumente, took over a departed author's business). With one role the result reports an exact totalCount; omit role for every role.
limitNoPage request, default 20; clamped to 100. Committee pages, and personNumber pages without role, count candidate roles and return each business once, so they may hold fewer businesses.
queryNoOne title substring, preserving punctuation and diacritics.
tagIdNoTopic tag ID from chparl_list_reference topic tags, matched as one whole element of the business's pipe-delimited Tags (12 does not match 1216). Without committeeId or personNumber, requires submittedFrom and submittedTo spanning at most 366 inclusive days and reports totalCount on the first page only; if a call runs out of time, retry with a narrower submission window.
authorNoSubstring of the published submitter label, not every co-signatory.
cursorNoOpaque nextCursor from a previous call with identical filters; omit to start.
typeIdNoBusiness type code from chparl_list_reference topic business_types.
languageNoMetadata language: de (default), fr, or it.de
statusIdNoCurrent status code from chparl_list_reference topic statuses.
sessionIdNoSubmission session ID from chparl_list_reference topic sessions.
committeeIdNoCommittee number from chparl_list_reference topic committees; matches any published committee role.
submittedToNoInclusive submission-date upper bound, YYYY-MM-DD.
personNumberNoExact member PersonNumber from chparl_search_members, chparl_get_member, a chparl_get_votes member row, or a chparl_search_transcripts passage speaker; former members included. Matches business where that member holds a published role, co-signatures included. Cannot combine with committeeId.
submittedFromNoInclusive submission-date lower bound, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoCombined clamp, short-page, or empty-result guidance.
hasMoreNoWhether older matching businesses remain.
businessesNoDistinct complete business summaries on this page.
nextCursorNoContinue after the smallest delivered business ID using identical filters.
provenanceNoAttribution, publication status, and source download dates.
totalCountNoOriginal-filter business total; omitted for author searches, committee searches, personNumber searches without role, and continuation pages of a tagId search without committeeId or personNumber, whose first page carries it.
returnedCountNoDistinct businesses actually delivered.
effectiveLimitNoEffective business or role-candidate limit after clamping.
effectiveFiltersNoEffective business discovery filters and defaults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page request, default 20; clamped to 100. Committee pages count candidate roles, and byte fitting may return fewer businesses."New value: +"Page request, default 20; clamped to 100. Committee pages, and personNumber pages without role, count candidate roles and return each business once, so they may hold fewer businesses."
    • addedInput schema / properties / personNumber
      Added value: +{
      +  "description": "Exact member PersonNumber from chparl_search_members, chparl_get_member, a chparl_get_votes member row, or a chparl_search_transcripts passage speaker; former members included. Matches business where that member holds a published role, co-signatures included. Cannot combine with committeeId.",
      +  "pattern": "^[1-9]\\d*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / role
      Added value: +{
      +  "description": "With personNumber only: one role the member holds. author (Urheber/Auteur/Autore), cosignatory (Mitunterzeichner/Cosignataire/Cofirmatario), spokesperson (Sprecher/Porte-parole/Relatore, e.g. for a parliamentary group's business), opponent (Bekämpfer/Opposant/Opposto), or successor (Übernehmer/Repreneur/Assumente, took over a departed author's business). With one role the result reports an exact totalCount; omit role for every role.",
      +  "enum": [
      +    "author",
      +    "cosignatory",
      +    "spokesperson",
      +    "opponent",
      +    "successor"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tagId
      Added value: +{
      +  "description": "Topic tag ID from chparl_list_reference topic tags, matched as one whole element of the business's pipe-delimited Tags (12 does not match 1216). Without committeeId or personNumber, requires submittedFrom and submittedTo spanning at most 366 inclusive days and reports totalCount on the first page only; if a call runs out of time, retry with a narrower submission window.",
      +  "pattern": "^[1-9]\\d*$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / effectiveFilters / properties / personNumber
      Added value: +{
      +  "description": "Member PersonNumber holding the roles.",
      +  "pattern": "^[1-9]\\d*$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / effectiveFilters / properties / role
      Added value: +{
      +  "description": "One member role.",
      +  "enum": [
      +    "author",
      +    "cosignatory",
      +    "spokesperson",
      +    "opponent",
      +    "successor"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / effectiveFilters / properties / tagId
      Added value: +{
      +  "description": "Topic tag ID matched as one whole Tags element.",
      +  "pattern": "^[1-9]\\d*$",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `incompatible_fields`: submittedFrom is after submittedTo. `invalid_cursor`: Cursor is malformed, unsupported, or belongs to different filters. `request_too_long`: The text filters make the URL-encoded Parliament request longer than its 2048-byte query-string limit. `upstream_rate_limited`: Parliament returned HTTP 429. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `incompatible_fields`: submittedFrom is after submittedTo, personNumber is combined with committeeId, or role is supplied without personNumber. `tag_scope_required`: tagId is used without committeeId or personNumber, and without submittedFrom and submittedTo spanning at most 366 inclusive days. `invalid_cursor`: Cursor is malformed, unsupported, or belongs to different filters. `request_too_long`: The text filters make the URL-encoded Parliament request longer than its 2048-byte query-string limit. `upstream_rate_limited`: Parliament returned HTTP 429. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "incompatible_fields",
      -  "invalid_cursor",
      -  "request_too_long",
      -  "upstream_rate_limited"
      -]New value: +[
      +  "incompatible_fields",
      +  "tag_scope_required",
      +  "invalid_cursor",
      +  "request_too_long",
      +  "upstream_rate_limited"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Combined clamp, short-page, size-fitting, or empty-result guidance."New value: +"Combined clamp, short-page, or empty-result guidance."
    • changedOutput schema / properties / totalCount / description
      Previous value: -"Original-filter business total, available only without author or committee filters."New value: +"Original-filter business total; omitted for author searches, committee searches, personNumber searches without role, and continuation pages of a tagId search without committeeId or personNumber, whose first page carries it."
  2. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `incompatible_fields`: submittedFrom is after submittedTo. `invalid_cursor`: Cursor is malformed, unsupported, or belongs to different filters. `upstream_rate_limited`: Parliament returned HTTP 429. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `incompatible_fields`: submittedFrom is after submittedTo. `invalid_cursor`: Cursor is malformed, unsupported, or belongs to different filters. `request_too_long`: The text filters make the URL-encoded Parliament request longer than its 2048-byte query-string limit. `upstream_rate_limited`: Parliament returned HTTP 429. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "incompatible_fields",
      -  "invalid_cursor",
      -  "upstream_rate_limited"
      -]New value: +[
      +  "incompatible_fields",
      +  "invalid_cursor",
      +  "request_too_long",
      +  "upstream_rate_limited"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses ordering ('newest canonical business IDs appear first'), an unusual paging quirk where committee and role-less personNumber pages count candidate roles and can return short pages, that author searches omit the total, that a single-role personNumber search returns an exact total, and that labels are untranslated de/fr/it. These are exactly the behaviors an agent cannot infer from annotations or schema.

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 filter inventory is front-loaded in the first sentence and the operational caveats follow in a logical order. It is dense for a 14-parameter tool and mostly earns its length, though the parenthetical tagId constraint duplicates schema text and could be trimmed.

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 an output schema already covering return shape and annotations covering the safety profile, the description fills the remaining gaps: pagination semantics, total-count variability by search mode, retry advice when a tagId call times out, and language behavior. Nothing an agent needs to call this correctly is missing.

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%, so every parameter is already documented in the input schema, including the 366-day tagId window and the personNumber/committeeId exclusion. The description largely restates the same filter inventory rather than adding parameter-level meaning beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource ('Search Swiss parliamentary business') and enumerates the distinct search dimensions (title substring, submitter label, type, status, session, dates, committee, member roles, tag), which lets an agent separate it from chparl_search_members or chparl_search_transcripts without opening a 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?

It explicitly routes follow-up work to siblings ('Use chparl_list_reference to resolve codes and chparl_get_business to read a returned businessId') and states the cursor contract ('follow nextCursor with unchanged filters'). It does not, however, say when an agent should prefer this search over the other chparl_search_* tools, so the when-not guidance is incomplete.

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.