Skip to main content
Glama

get_school_holidays

Read-onlyIdempotent

Retrieve Swiss school holiday periods for a specified year and canton, or all cantons, to plan schedules and travel.

Instructions

School holiday periods for a year, by canton

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": {
      "year": "<year>"
    },
    "name": "get_school_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYese.g. 2026
cantonNoCanton code, e.g. ZH (omit for all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Two-letter canton code (e.g. ZH, BE, GE, BS, TI). If omitted, returns school holidays for all cantons."New value: +"Canton code, e.g. ZH (omit for all)"
    • changedInput schema / properties / year / description
      Previous value: -"Year (e.g. 2026)"New value: +"e.g. 2026"
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. However, the description adds nothing beyond them: no word on the shape of a 'holiday period' (date range vs single day), whether cantons without data return empty, or how results are ordered.

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?

A single eight-word fragment with zero filler, and the scope constraint is front-loaded. Nothing could be trimmed without losing meaning.

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 two-parameter read tool with full schema coverage and annotations, this is barely sufficient. What is missing is the nature of the returned data, i.e. whether a holiday period is a start/end pair per canton or a flat list of dates, which an agent needs in order to present results correctly.

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%, including the key detail 'omit for all' on canton and an example year, so the baseline is 3. The description's 'by canton' and 'for a year' merely restate what the schema already documents.

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?

'School holiday periods for a year, by canton' names a specific resource (school holidays, not public holidays) and its two scoping dimensions (year, canton). It implicitly separates itself from sibling get_public_holidays via the word 'school', but never routes explicitly.

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?

There is no when-to-use guidance, no mention of alternatives such as get_public_holidays or is_holiday_today, and no stated prerequisites. An agent must infer from the name alone which holiday tool to pick.

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