Skip to main content
Glama

get_public_holidays

Read-onlyIdempotent

Retrieve Swiss public holidays for a given year, nationally or filtered by canton code, to plan schedules and avoid conflicts.

Instructions

Public holidays for a year, national and cantonal

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_public_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 all Swiss holidays."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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description adds the coverage model (national plus cantonal aggregation), but says nothing about behavior for an unknown canton code or multiple cantons.

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?

A single eleven-word fragment with zero filler, and the scope qualifier is right where the reader needs it. It stops just short of 5 because the missing verb leaves the operation ('list/return') implied rather than stated.

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 two-parameter read-only lookup with full schema coverage and rich annotations, the description covers the essentials. It is still thin on sibling disambiguation and on any edge behavior, which is the only real gap left.

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% and both parameters are documented inline, including 'omit for all' for canton, so the baseline is 3. The phrase 'national and cantonal' loosely reinforces what the canton parameter controls but adds no new meaning beyond the schema.

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 fragment names a specific resource (public holidays) plus its scope: one year, at national and cantonal levels. That is enough to distinguish it from most siblings, but it never mentions get_school_holidays or is_holiday_today, so an agent must still infer which holiday tool it wants.

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 or when-not-to-use guidance. Nothing tells the agent to pick this over is_holiday_today for a single-date check or over get_school_holidays for school calendars; the only implicit cue is 'for a year'.

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