Skip to main content
Glama

is_holiday_today

Read-onlyIdempotent

Determine whether today is a public holiday in Switzerland, optionally filtered by canton, so you can check if offices, shops, or services are closed before planning your day.

Instructions

Whether today is a public holiday

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": "is_holiday_today"
  }
}

Input Schema

NameRequiredDescriptionDefault
cantonNoCanton code, e.g. ZH (omit for nationwide only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Two-letter canton code (e.g. ZH, BE, GE). If omitted, checks nationwide holidays only."New value: +"Canton code, e.g. ZH (omit for nationwide only)"
  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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. Beyond that the description adds nothing: it does not state the return shape (presumably a boolean), whether the answer is canton-scoped or nationwide by default, or which timezone defines 'today', even though 'today' is inherently ambiguous for an open-world tool.

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 short sentence with zero waste, front-loaded with the resource and the temporal scope. Nothing superfluous is present; the brevity problem here is under-specification, which is captured in other dimensions.

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?

The tool is simple (one optional param, no output schema, annotations present), so the description does not need to be long. However, it leaves out the return type and the relationship to get_public_holidays, both of which an agent needs to call this correctly rather than a sibling.

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 the single optional canton parameter is well documented in the schema, including the 'omit for nationwide only' default. The description mentions nothing about canton, so it adds no meaning beyond the schema — 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?

The description names a specific resource (public holiday) and scope (today), forming a clear boolean query that an agent can understand at a glance. It does not, however, distinguish itself from the sibling get_public_holidays, so the agent must infer the difference (single-day check vs. calendar listing) on its own.

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 at all: no statement that this is a lightweight yes/no check versus get_public_holidays for a date range, and no mention of what happens if a canton is omitted. The agent is left to infer the routing decision purely from the 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