Skip to main content
Glama

Time of Meeting

Public holidays

get_holidays
Read-onlyIdempotent

List public holidays for a country, an optional ISO 3166-2 region, or a city. Use when the user asks whether a date is a holiday somewhere, or which days are holidays in a year. Pass one year, a list of years so 2026, 2027, and 2028 can come back together, or a date range. Each holiday has the date, the weekday, whether it falls on Saturday or Sunday, whether it creates a long weekend of three or more days with Saturday and Sunday, the local name, the English name, whether it is regional, the region codes, the file it came from, and the calendar page URL. The same holiday list marks the planner timeline.

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city. Its country and region are used. City name or a city id from a city search. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives.
yearNoOne calendar year. Defaults to the current year when years, start_date, and end_date are omitted. Do not pass year and years together.
yearsNoCalendar years, such as [2026, 2027, 2028]. A gap is not filled in. Do not pass years with year or with a date range.
regionNoOptional ISO 3166-2 code, such as DE-BY or GB-SCT. National holidays are included with that region's own days.
countryNoISO 3166-1 alpha-2 code or English country name. UK is accepted for the United Kingdom.
end_dateNoLast day, YYYY-MM-DD.
start_dateNoFirst day, YYYY-MM-DD. Use with end_date instead of year. At most 366 days.

Output Schema

NameRequiredDescriptionDefault
cityYes
yearYes
errorNo
yearsYes
regionYes
sourceYes
countryYes
end_dateYes
holidaysYes
candidatesNo
start_dateYes
alternativesNoOther cities that matched the same name, after the best-ranked city was chosen. The order is the site search order: match, then priority, then population.
country_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "country"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "city"
      +    ]
      +  }
      +]
    • removedInput schema / required
      Removed value: -[]
  2. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"Optional city. Its country and region are used. City name or a city id from search_cities. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives."New value: +"Optional city. Its country and region are used. City name or a city id from a city search. Spelling and accents are flexible. When several cities share a name, the best match from the site search is used and the others come back in alternatives."
  3. Changed2 schema fields changed
    • removedOutput schema / properties / link
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "country",
      -  "country_name",
      -  "region",
      -  "city",
      -  "year",
      -  "years",
      -  "start_date",
      -  "end_date",
      -  "source",
      -  "link",
      -  "holidays"
      -]New value: +[
      +  "country",
      +  "country_name",
      +  "region",
      +  "city",
      +  "year",
      +  "years",
      +  "start_date",
      +  "end_date",
      +  "source",
      +  "holidays"
      +]
  4. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavior: year defaults to the current year, gaps in a year list are not filled in, and regional requests also include national holidays. Beyond that it mostly enumerates return fields, which the existing output schema already carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the usage sentence are front-loaded and efficient. The long middle clause enumerating ten return attributes is bulky and largely duplicates the output schema, costing space without adding decision-relevant information.

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 7-parameter tool with full schema coverage and an output schema, the description covers purpose, triggering questions, the three mutually exclusive time-selection modes, and default behavior. What remains missing is minor: error behavior for invalid country codes and how results are ordered.

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%, so the baseline is 3. The description reinforces the year / years / date-range exclusivity and gives the motivation ('so 2026, 2027, and 2028 can come back together'), but adds no format or syntax detail beyond what the schema already documents.

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?

Opens with a specific verb and resource ('List public holidays') and names the three scoping keys (country, ISO 3166-2 region, city), which is enough to distinguish it from calendar-math siblings like working_days_between or add_business_days. It stops short of explicitly contrasting with any named sibling, so it lands at 4 rather than 5.

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?

Gives concrete triggering questions: 'whether a date is a holiday somewhere' and 'which days are holidays in a year'. That is a clear usage context, but there are no exclusions or named alternatives for cases like counting working days, which nearby siblings handle.

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