Skip to main content
Glama

School holidays

get_school_holidays
Read-only

Retrieve school holiday periods for a Swiss canton and optional year to check term breaks for planning.

Instructions

School holiday periods for a Swiss canton and year.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear (default: current year)
cantonYesCanton code, e.g. 'ZH', 'BE', 'VD'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

C2.8/5.0
Behavior2/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 nothing beyond that: no data source, update cadence, or reliability caveat for an open-world lookup, and no indication of what the returned periods look like.

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?

A single short sentence with no wasted words, but its brevity reflects under-specification rather than tightness. It is front-loaded but leaves out information a caller would need.

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?

With no output schema, the description should at least outline the return shape (periods with names and date ranges), and it does not. For a simple two-parameter read tool this is a modest gap, but the response format is entirely undocumented.

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 the canton example codes and the year default (current year) already documented in the schema. The description only restates 'canton and year' and adds no new semantics such as supported canton codes or valid year range.

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?

States a specific resource (school holiday periods) and bounds it to a Swiss canton and year, which inherently separates it from get_public_holidays by the 'school' qualifier. It stops short of explicitly naming or excluding the sibling, so it is clear rather than fully differentiated.

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 guidance on when to use this versus get_public_holidays, no note on which cantons are covered, and no prerequisites such as whether holidays differ by municipality or school level. Usage is only implied by the resource name.

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