Skip to main content
Glama

get_committee_meetings

Read-onlyIdempotent

Retrieve the Swiss federal parliament committee meeting schedule, optionally filtered by committee group ID and limited by a result cap.

Instructions

Federal parliament committee meeting schedule

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_committee_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 20
group_idNoCommittee group ID (omit for all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / group_id / description
      Previous value: -"Committee group ID to filter (optional — omit for all committees)"New value: +"Committee group ID (omit for all)"
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Max meetings to return (default: 5, max: 20)"New value: +"max 20"
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds nothing else: it does not say whether meetings returned are upcoming, current, or historical, how they are ordered, or what happens when limit is hit beyond the schema's 'max 20'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with zero waste, but this is terseness rather than well-structured conciseness — there is no front-loaded verb or scope statement to anchor the agent. Under-specification rather than bloat.

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

Completeness2/5

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

The tool is simple (2 optional params, no output schema, annotations present), yet the description omits the one thing an agent cannot infer from structured fields: the temporal window of the schedule. Without a date parameter, whether this returns past or future meetings is unknowable from the definition.

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 100%, with both limit and group_id documented inline, so the description has no semantical burden to carry and adds nothing beyond it. Baseline 3 applies.

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?

Names a specific resource ('committee meeting schedule') and scopes it to 'Federal parliament', which distinguishes it from the sibling get_session_schedule (plenary sessions) and search_parliament_business. It is a noun fragment with no verb, but the resource is unambiguous.

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?

No guidance on when to use this versus get_session_schedule, get_parliament_members, or search_parliament_business, which all live in the same parliamentary domain. The agent must infer selection purely from the noun phrase.

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