Skip to main content
Glama

get_parliament_members

Read-onlyIdempotent

Retrieve Swiss federal parliament members from the National Council and Council of States, filtered by canton, party, or active status.

Instructions

Federal parliament members (National Council, Council of States), filterable by canton/party

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": "get_parliament_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 50
partyNoParty name/abbreviation, e.g. SVP, SP, FDP, Grüne, Mitte
activeNoOnly currently seated members
cantonNoCanton name in German, e.g. Zürich, Genf, Waadt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.9.0
    • addedInput schema / properties / active / default
      Added value: +true
    • changedInput schema / properties / active / description
      Previous value: -"Only active (currently seated) members (default: true)"New value: +"Only currently seated members"
    • changedInput schema / properties / canton / description
      Previous value: -"Canton name in German to filter by (e.g. 'Zürich', 'Bern', 'Genf', 'Waadt')"New value: +"Canton name in German, e.g. Zürich, Genf, Waadt"
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default: 10, max: 50)"New value: +"max 50"
    • changedInput schema / properties / party / description
      Previous value: -"Party name or abbreviation to search (e.g. 'SVP', 'SP', 'FDP', 'Grüne', 'Mitte')"New value: +"Party name/abbreviation, e.g. SVP, SP, FDP, Grüne, Mitte"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and mutation behavior are fully covered structurally. The description adds essentially nothing behavioral beyond that: it does not mention the default of active=true, the 50-item cap, or what a member record contains, so it earns little credit over 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?

A single front-loaded fragment with zero filler and the key scoping (both chambers, canton/party filters) up front. It is telegraphic rather than a complete sentence, but nothing in it is wasted.

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

Completeness3/5

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

With four optional parameters, no output schema, and no annotations gaps, the minimum bar is met, but an agent still cannot tell what a returned member looks like (name, party, canton, chamber, council) or how results are ordered/paginated. For a list tool with no output schema, that leaves a noticeable hole.

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%, including examples for party (SVP, SP, FDP) and canton (Zürich, Genf), so the schema does the heavy lifting. The description only restates that canton and party are usable filters, adding no format or edge-case detail (e.g. case sensitivity, partial matching) beyond the schema.

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 names a precise resource ('Federal parliament members') and scopes it to both chambers (National Council, Council of States), which is specific enough to separate it from siblings like get_parliament_votes or search_parliament_speeches. It does not explicitly name or contrast those siblings, which keeps it below 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 Guidelines2/5

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

'filterable by canton/party' hints at how the tool is used but gives no when-to-use guidance, no prerequisites, and no indication of when a sibling (e.g. get_parliament_votes for voting behavior) would be the better choice. An agent must infer the retrieval-only role from the noun phrase alone.

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