Skip to main content
Glama

Find public holidays

find_holidays
Read-onlyIdempotent

Use this when the user wants the list of public holidays for a country (and optionally a state or region) in a year, for example to check what a printed calendar will mark ("bank holidays 2027 UK", "Texas holidays 2027", "Feiertage Bayern 2027"). Returns each holiday with its date, weekday and type, including observed weekdays when a holiday falls on a weekend; observances are optional. Does not count business days between dates, and does not cover school terms or religious calendars outside the holiday data.

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": {
      "country": "<country>"
    },
    "name": "find_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear, e.g. 2027. Default: next year from October on, otherwise this year.
countryYesCountry: ISO two-letter code or name, e.g. US, GB, DE, PL, FR, JP, BR, AU, CA.
languageNoLanguage for month and weekday names: en (default), pl, de, es, fr, it, pt, nl or ja. Holiday names use this language when the country's data has it, else English. Example: de
subdivisionNoOptional state, province or region for local holidays, e.g. TX or CA (US), BY (Bavaria, DE), SCT (Scotland), NSW (AU), ON (CA).
include_observancesNoAlso show observances, bank and optional days (e.g. Mother's Day, Valentine's Day, Christmas Eve). Default false: public holidays only.

Output Schema

NameRequiredDescriptionDefault
kindYes
yearYes
countYes
notesYes
inputsYes
regionYes
holidaysYes
on_weekdaysYes
public_countYes
include_observancesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds useful behavioral detail about observed weekdays, optional observances, and scope exclusions. It does not discuss authentication or rate limits, which is acceptable for this public-holiday lookup, but the disclosure remains moderately rich rather than exhaustive.

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?

The description is front-loaded with the primary usage condition and remains compact across three sentences. The examples and exclusions each earn their place by helping an agent route the request correctly without wasting words.

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 rich annotations, full schema coverage, and presence of an output schema, the description provides sufficient context: when to use it, what it returns at a high level, what it excludes, and how observances are handled. An agent can call this tool correctly without additional description text.

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 the schema already documents all five parameters, including country formats, year defaults, language codes, subdivision examples, and observance behavior. The description reinforces country/year/subdivision usage through example queries but adds little parameter semantics beyond what the schema already provides, so the baseline score of 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 clearly states the specific resource and scope: public holidays for a country, optionally a state or region, in a year. It distinguishes the tool from adjacent tasks such as business-day counting and school/religious calendars, but it does not explicitly differentiate it from the sibling tool generate_calendar.

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?

It opens with explicit usage guidance: 'Use this when the user wants the list of public holidays...' and supplies realistic examples such as 'bank holidays 2027 UK' and 'Texas holidays 2027'. It also states what the tool does not do, but it does not name generate_calendar as the alternative for calendar-generation use cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources