Skip to main content
Glama

List parliamentary committees

list_parliament_committees
Read-only

Lists Swiss Federal Assembly committees by council and name or abbreviation fragment, returning committee number, name, abbreviation, council and type for parliamentary research.

Instructions

List committees of the Federal Assembly (legislative committees such as WAK-N/WAK-S economy, SiK security, UREK environment, SGK health, plus supervisory committees GPK/FinK and joint bodies). Returns committee number, name, abbreviation, council (NR/SR/BV) and type. Filter by council and a name/abbreviation fragment. Examples: {council:'NR'}; {query:'Wirtschaft'}; {query:'SGK'}. Use get_committee_members for the members.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoName or abbreviation fragment, e.g. 'WAK', 'Gesundheit'
councilNoNR = National Council, SR = Council of Statesall
languageNoDE
include_inactiveNoInclude dissolved/historical committees
include_subcommitteesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/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 the safety profile is covered. The description adds useful behavioral detail by listing what is returned (number, name, abbreviation, council, type) and noting that supervisory and joint bodies are included. However, it says nothing about result volume, the 60/200 limit behavior, or ordering, which matter for a list endpoint.

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 sentence order is well front-loaded: purpose, then scope taxonomy, then return fields, then filters, then examples, then the sibling handoff. The parenthetical committee list is dense but genuinely informative for recognizing the resource. Slightly long, yet every clause carries content.

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 no output schema, the description usefully enumerates the returned fields, and it covers the main filters and the sibling alternative. Gaps remain for a 6-parameter list tool: nothing about the default/maximum result count, the language parameter's effect on names, or what include_subcommittees and include_inactive actually change in the response.

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 coverage is 50%, so the description must compensate — it explains the two main filters and gives value examples for 'query' and 'council' (NR/SR), plus implicitly that 'all' is broad. It leaves limit, language (DE default), include_inactive, and include_subcommittees unaddressed beyond the bare schema descriptions, 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?

The description opens with a specific verb and resource ('List committees of the Federal Assembly') and scopes it further by naming committee families (WAK-N/WAK-S, SiK, UREK, SGK, GPK/FinK, joint bodies). It also enumerates the returned fields and distinguishes the resource from parliamentary groups and from member data, so an agent can tell exactly what this tool serves.

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?

Usage is grounded with concrete call examples ('{council:\'NR\'}', '{query:\'Wirtschaft\'}', '{query:\'SGK\'}') and an explicit handoff: 'Use get_committee_members for the members.' That clearly routes the agent away from a sibling tool. It lacks explicit when-not-to-use conditions or guidance on combining filters, hence not a 5.

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