Skip to main content
Glama

get_session_schedule

Retrieve upcoming and recent Swiss parliament session schedules, including session names, dates, and types, to track legislative activities.

Instructions

Get upcoming and recent Swiss parliament sessions (Sessionen). Shows session names, dates and types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of sessions to return (default: 5, max: 20)

Implementation Reference

  • Implementation of the get_session_schedule tool, which fetches parliamentary session data from OpenParlData.
    async function getSessionSchedule(args: {
      limit?: number;
    }): Promise<string> {
      const limit = Math.min(args.limit ?? 5, 20);
      const url = buildUrl("/meetings/", {
        body_key: "CHE",
        type: "session",
        sort_by: "-begin_date",
        lang: "de",
        lang_format: "flat",
        limit,
      });
      const resp = await apiFetch<MeetingRecord>(url);
    
      const sessions = resp.data.map((m) => ({
        id: m.id,
        name: m.name_de,
        abbreviation: m.abbreviation,
        type: m.type_external_de,
        startDate: m.begin_date ? m.begin_date.split("T")[0] : null,
        endDate: m.end_date ? m.end_date.split("T")[0] : null,
        url: m.url_external_de,
      }));
    
      return truncate(
        JSON.stringify({
          count: sessions.length,
          total: resp.meta.total_records,
          sessions,
        })
      );
    }
  • Definition of the get_session_schedule tool schema.
      name: "get_session_schedule",
      description:
        "Get upcoming and recent Swiss parliament sessions (Sessionen). Shows session names, dates and types.",
      inputSchema: {
        type: "object" as const,
        properties: {
          limit: {
            type: "number",
            description: "Number of sessions to return (default: 5, max: 20)",
          },
        },
      },
    },
  • Registration/dispatch logic for get_session_schedule in the main handler function.
    case "get_session_schedule":
      return getSessionSchedule(args as { limit?: number });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what data is returned (session names, dates, types) but doesn't mention important behavioral aspects like whether this is a read-only operation, how 'upcoming and recent' is defined, time ranges, sorting order, pagination, or error conditions. For a data retrieval tool with no annotations, this leaves significant gaps.

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 description is efficiently structured in a single sentence that states the core purpose and what data is returned. There's no wasted verbiage or redundancy. However, it could be slightly more front-loaded by specifying the exact scope ('Swiss parliament sessions') earlier in the sentence.

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?

For a simple read operation with one well-documented parameter and no output schema, the description provides the basic purpose and return data. However, it lacks important context about behavioral aspects (time ranges, sorting, error handling) and doesn't explain the relationship to other parliament tools. Without annotations or output schema, the description should provide more complete operational context.

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?

The description adds no parameter information beyond what's already in the schema (which has 100% coverage). The schema fully documents the single 'limit' parameter with its type, description, default value, and maximum. The description doesn't provide additional context about parameter usage or semantics, 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 upcoming and recent Swiss parliament sessions' with specific resources (session names, dates, types). It distinguishes from siblings by focusing on parliament sessions rather than other Swiss data like weather, traffic, or companies. However, it doesn't explicitly differentiate from 'get_committee_meetings' or 'get_parliamentary_documents' which might be related parliament tools.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of when this tool is appropriate versus other parliament-related tools like 'get_parliamentary_documents' or 'get_parliament_members', nor any prerequisites or constraints beyond what's in the parameter description.

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