Skip to main content
Glama
malkreide

swiss-school-calendar-mcp

by malkreide

get_school_holidays

Read-onlyIdempotent

Retrieve school holiday periods for any Swiss canton within a specified date range, with optional filtering by school type.

Instructions

Return school holiday periods for one canton in a date range.

Look up a canton's school holidays for planning within an explicit from/to window (term breaks, parent events, campaigns). Apparent duplicates are the same period per Schulart; set school_type to collapse them. Cantons that do not differentiate return one table.

Args: canton: ISO subdivision code, e.g. CH-ZH. valid_from: Inclusive start date, YYYY-MM-DD. valid_to: Inclusive end date, YYYY-MM-DD. school_type: Optional Schulart suffix -- VS, MS, BS or EO. Use VS for compulsory schooling (Volksschule). language: DE, FR, IT or EN.

Records that look duplicated are usually the same period published for a different Schulart. Set school_type to collapse them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cantonYesISO code, e.g. CH-ZH
languageNoDE
valid_toYesDate as YYYY-MM-DD
valid_fromYesDate as YYYY-MM-DD
school_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoHuman-readable caveat, set when provenance is 'degraded'.
countYes
sourceYesAttribution string of the upstream source.
holidaysYes
match_typeNoHow the lookup key resolved (audit ARCH-003): 'exact' (code or full name / validated canton), 'fuzzy' (a single prefix match was assumed) or 'none' (nothing matched — see `note` for suggestions).exact
provenanceYeslive_api = freshly fetched, cached = in-memory cache, degraded = upstream unreachable, stale or empty payload.
retrieved_atYesISO-8601 UTC timestamp of the underlying fetch.
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description discloses duplicate handling and how to collapse them via 'school_type', and explains behavior for cantons that don't differentiate. This adds significant context.

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 well-structured with tags but slightly verbose. It could be tightened without losing clarity, but remains efficient.

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

Completeness5/5

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

Given the presence of an output schema, the description adequately covers use case, parameters, and behavioral quirks. It is complete for a tool of moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The 'Args' section provides clear explanations for all 5 parameters, including format examples and guidance on 'school_type' values. This surpasses the schema descriptions, which had 60% coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'return', resource 'school holiday periods', and constraints (one canton, date range). It distinguishes from siblings like 'get_public_holidays' by focusing on school holidays and canton-specific scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'use_case' tag explicitly describes when to use the tool (planning within an explicit from/to window). It does not provide direct exclusions but the sibling list implies alternatives for other holiday types.

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/malkreide/swiss-holidays-mcp'

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