Skip to main content
Glama

get_committee_meetings

Retrieve Swiss parliament committee meeting schedules. Filter by committee group ID and set result limits to find specific meeting information.

Instructions

Get Swiss parliament committee/commission meeting schedule. Optionally filter by committee group ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNoCommittee group ID to filter (optional — omit for all committees)
limitNoMax meetings to return (default: 5, max: 20)

Implementation Reference

  • The implementation of the getCommitteeMeetings function which fetches and formats committee meeting data.
    async function getCommitteeMeetings(args: {
      group_id?: number;
      limit?: number;
    }): Promise<string> {
      const limit = Math.min(args.limit ?? 5, 20);
      const params: Record<string, string | number | boolean | undefined> = {
        body_key: "CHE",
        type: "meeting",
        sort_by: "-begin_date",
        lang: "de",
        lang_format: "flat",
        limit,
      };
      if (args.group_id !== undefined) {
        params.group_id = args.group_id;
      }
    
      const url = buildUrl("/meetings/", params);
      const resp = await apiFetch<MeetingRecord>(url);
    
      const meetings = resp.data.map((m) => ({
        id: m.id,
        name: m.name_de,
        date: m.begin_date ? m.begin_date.split("T")[0] : null,
        endDate: m.end_date ? m.end_date.split("T")[0] : null,
        state: m.state,
        groupId: m.group_id,
        url: m.url_external_de,
      }));
    
      return truncate(
        JSON.stringify({
          count: meetings.length,
          total: resp.meta.total_records,
          meetings,
        })
      );
    }
  • The registration and schema definition for the get_committee_meetings tool.
    {
      name: "get_committee_meetings",
      description:
        "Get Swiss parliament committee/commission meeting schedule. Optionally filter by committee group ID.",
      inputSchema: {
        type: "object" as const,
        properties: {
          group_id: {
            type: "number",
            description:
              "Committee group ID to filter (optional — omit for all committees)",
          },
          limit: {
            type: "number",
            description: "Max meetings to return (default: 5, max: 20)",
          },
        },
      },
    },
  • The dispatcher case that maps the get_committee_meetings tool name to its handler function.
    case "get_committee_meetings":
      return getCommitteeMeetings(
        args as { group_id?: number; limit?: number }
      );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions optional filtering but doesn't describe other behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what the return format looks like (e.g., list of meetings with dates/times). For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that front-loads the core purpose and includes optional filtering information. There is no wasted language, and it's appropriately sized for a simple retrieval tool with two parameters.

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?

Given the tool's low complexity (2 optional parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and hints at filtering but lacks details on behavioral aspects (e.g., read-only nature, return format) that would be important for an agent to use it correctly. Without annotations or an output schema, the description should do more to compensate, but it only meets the bare minimum.

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%, meaning the input schema already fully documents both parameters (group_id and limit). The description adds minimal value beyond the schema by mentioning 'Optionally filter by committee group ID,' which aligns with the schema's description for group_id. It doesn't provide additional context like typical group_id values or usage examples, so the baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Get Swiss parliament committee/commission meeting schedule.' It specifies the resource (meeting schedule) and scope (Swiss parliament committees/commissions). However, it doesn't explicitly differentiate from sibling tools like 'get_session_schedule' or 'search_parliament_business,' which might also involve parliamentary scheduling or meetings.

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?

The description provides implied usage guidance by mentioning 'Optionally filter by committee group ID,' suggesting this tool is for retrieving meeting schedules with optional filtering. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_session_schedule' or 'search_parliament_business,' nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server