Skip to main content
Glama

holidays

Read-only

Look up public holidays for a year or calculate business days between two dates minus holidays, with built-in support for DE, AT, CH, US, GB, FR and online lookup for other countries.

Instructions

Public holidays of a year, or business days start..end minus holidays. Built in: DE (+16 states via region, e.g. BY), AT, CH, US, GB, FR; others online.

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

Input Schema

NameRequiredDescriptionDefault
endNo
yearNo
startNo
regionNo
countryNodefault DE
include_endNodefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, so safety is covered. The description does add genuinely useful behavioral context: an explicit coverage list of built-in countries and the note that others are fetched 'online', implying network latency or failure modes for unsupported countries. It stops short of saying what occurs when the online lookup fails or what the returned data looks like.

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?

Two dense sentences with zero filler, and the primary capability is front-loaded before the country coverage list. The telegraphic phrasing ('Built in: DE (+16 states via region, e.g. BY)') is efficient but slightly cryptic on first read.

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 six-parameter, zero-required, no-output-schema utility this is close to sufficient: coverage, defaults, and the dual mode are all conveyed. Missing pieces are the include_end flag, date formats, and the shape of the result — modest gaps rather than blocking ones.

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

Parameters4/5

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

At 33% schema coverage the description must compensate, and it partially does: it clarifies that 'region' selects sub-national entities (BY for a German state), that 'country' defaults to DE, and that 'start'/'end' define a holiday-subtracted business-day span. The 'include_end' parameter is never explained anywhere, and the date string format for start/end is left unspecified — gaps that a 3 would also fit. The region example and default-country note push it just above baseline.

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 the concrete resource (public holidays) and the second capability (business days in a range minus holidays), which lets an agent tell it apart from generic siblings like 'calendar' or 'date_diff'. The opening is a noun phrase rather than a verb, but the domain is unmistakable.

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?

It implicitly reveals two modes of operation — a single 'year' query versus a 'start..end' business-day computation — which is real usage guidance for choosing parameters. However, it never states prerequisites, exclusions, or which sibling to prefer for adjacent date math, and gives no rule for what happens if both year and start/end are supplied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.