Skip to main content
Glama

Search Federal Assembly members

search_council_members
Read-only

Find members of Switzerland’s National Council and Council of States by last-name fragment, canton, or party abbreviation, with options to limit results and include only current members.

Instructions

Search members of the National Council and Council of States (current by default) by last name (case-insensitive fragment), canton or party abbreviation.

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

Input Schema

NameRequiredDescriptionDefault
nameNoLast-name fragment (case-insensitive)
limitNo
partyNoParty abbreviation as used in German, case-insensitive, e.g. 'SVP', 'SP', 'FDP-Liberale', 'M-E', 'GRÜNE', 'glp'
cantonNoCanton abbreviation, e.g. 'ZH'
active_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the useful default that only current members are returned, but says nothing about result caps, ordering, or pagination behavior. Reasonable but thin beyond the structured fields.

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 sentence with the resource and searchable dimensions stated first and no filler. Dense enough to read cleanly, though the multiple parentheticals make it slightly clause-heavy.

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?

There is no output schema, so the description ideally would say what a member record contains and how many results come back, which it does not. It is adequate for selecting the tool and forming a query, but leaves return-shape and limit semantics undocumented.

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 60%, with the two undocumented parameters being limit and active_only. The description partially compensates by clarifying that matching is a case-insensitive last-name fragment and that results default to current members, which maps to active_only. It still never explains limit, so it cannot fully close the coverage gap.

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?

States a specific verb and resource ('Search members of the National Council and Council of States') plus the searchable dimensions, so an agent knows exactly what it retrieves. It does not differentiate from plausible siblings like search_local_politicians or get_committee_members, so it stops short of 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 Guidelines3/5

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

Usage is only implied: the parenthetical '(current by default)' hints that historical members are reachable, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for cantonal/local politicians. The agent must infer routing from the tool name.

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