Skip to main content
Glama

Public holidays

get_public_holidays
Read-only

Retrieve Swiss public holidays for a given year, optionally filtered by canton, including nationwide and cantonal dates.

Instructions

Public holidays in Switzerland for a year, optionally scoped to a canton (two-letter code). Includes nationwide and cantonal holidays.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear (default: current year)
cantonNoCanton code, e.g. 'ZH', 'GE' (default: whole country)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior3/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 useful scope context — that results include both nationwide and cantonal holidays, and that omitting canton means the whole country — but says nothing about the shape of the response (dates, names, ordering) for a tool with no output schema.

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?

Two short sentences, front-loaded with the resource and scope, with the optional narrowing stated immediately after. No filler or redundant phrasing.

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

Completeness4/5

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

For a simple two-optional-parameter read tool with full schema coverage and annotations, the description covers scope, defaults, and what is included. The only gap is the return shape (list of dates vs. named holidays), which matters slightly more because no output schema exists.

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%, so both parameters are already documented in the schema, including the 'ZH'/'GE' examples and the current-year default. The description's 'two-letter code' and 'default: whole country' restate rather than extend the schema, so the baseline 3 applies.

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 (public holidays), a geographic scope (Switzerland), and an optional narrowing dimension (canton), which cleanly separates it from the sibling get_school_holidays. It stops short of explicitly naming that sibling or any other alternative, so it is clear but not maximally differentiated.

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

Usage Guidelines3/5

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

The description implies when the tool applies (a year, optionally a canton) but gives no explicit when-to-use/when-not-to-use guidance and no mention of alternatives such as school holidays. Usage is inferable from the scope statement rather than stated.

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