Skip to main content
Glama

Members of a parliamentary committee

get_committee_members
Read-only

Retrieve current members of a Swiss Federal Assembly committee by abbreviation, number, or name fragment, with function, party, parliamentary group, canton, and council for each member.

Instructions

Current members of one Federal Assembly committee with their function (president, vice-president, member), party, parliamentary group, canton and council. Identify the committee by abbreviation ('WAK-N', 'SGK-S', 'GPK-N'), committee number, or a name fragment ('Wirtschaft und Abgaben'). Use list_parliament_committees to find committees.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "committee": "<committee>"
    },
    "name": "get_committee_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
languageNoDE
committeeYesAbbreviation (e.g. 'WAK-N'), committee number (e.g. '5') or name fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already covered; the description adds the useful behavioral fact that it returns exactly one committee's members with a fixed set of attributes. It omits that results are capped by a limit defaulting to 60 (max 100), which would matter for large committees, keeping it from a 5.

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?

Two tight sentences: the first front-loads what is returned, the second covers how to identify the committee plus the fallback tool. No redundant restatement of the title or name.

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

Completeness4/5

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

With no output schema, listing the returned member attributes is exactly the right compensation, and identifier formats are covered. The remaining gap is operational detail about result limits and language selection, which an agent would need to know to call it optimally.

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?

With only 33% schema coverage, the description carries the burden, and it does well for 'committee' by spelling out abbreviation, number and name-fragment forms with examples. However, the 'limit' and 'language' parameters are explained in neither the schema nor the description, so the compensation is only partial.

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 ('Current members of one Federal Assembly committee') and enumerates exactly what each member record contains: function, party, parliamentary group, canton and council. This is distinguishable from list_parliament_committees without opening either 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?

Explicitly routes the agent to list_parliament_committees when it needs to discover committees, and explains the three ways to identify one (abbreviation, number, name fragment). It stops short of stating when-not to use this tool, but the discovery-vs-lookup split is clear.

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