Skip to main content
Glama

List public holidays

list_holidays
Read-onlyIdempotent

Use this when the user asks which public holidays (bank holidays) a country or a state/region has in a year, e.g. 'Poland public holidays 2026' or 'Texas state holidays 2027', usually to plan working days. Returns each holiday with date, weekday, English name and whether it falls on a weekend, including the observed weekday off when a holiday falls on a weekend, plus a CSV file. Does not include school holidays, religious observances that are not days off, or company-specific closures. Do not use to check whether a stock exchange is open.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear, e.g. 2026. Defaults to the current year.
countryYesCountry as an ISO two-letter code, e.g. PL, US, GB, DE.
subdivisionNoOptional state/region code, e.g. TX (Texas), BY (Bavaria), SCT (Scotland).
weekend_daysNoWeekend days used to flag holidays falling on a weekend, e.g. ["friday","saturday"]. Default from the country.
include_bank_holidaysNoAlso list bank-only closing days where available, e.g. Dec 24 in Germany. Default false.

Output Schema

NameRequiredDescriptionDefault
kindYes
yearYes
countYes
notesYes
inputsYes
regionYes
summaryYes
holidaysYes
downloadsYes
on_weekdaysYes
weekend_daysYes
observed_daysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered structurally. The description adds real value beyond that: the returned fields (date, weekday, English name, weekend flag, observed weekday off) and the CSV attachment. It does not cover rate limits, pagination, or coverage gaps in country support, so it is solid but not 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?

Front-loads the trigger and examples, then the return payload, then the exclusions – a logical order with no filler. Four sentences that each carry distinct information (when, what you get, what is excluded, what this is not).

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 five parameters, one required, full schema coverage and an output schema, the description covers the remaining gaps: invocation intent, payload shape, and negative boundaries. Nothing an agent needs to select or call this correctly is missing.

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 every parameter is already documented with examples and defaults; the description adds no syntax or format detail beyond that. There is a mild tension worth noting: the description calls these 'public holidays (bank holidays)' while include_bank_holidays defaults to false, so bank-only closing days are not returned unless explicitly requested.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list public holidays) plus the scoping dimensions (country or state/region, year) and gives concrete example queries. An agent can immediately distinguish this from calculate_date_offset and count_days_between, which do arithmetic rather than enumerating holidays.

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

Usage Guidelines5/5

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

Explicit when-to-use trigger (user asks which public holidays a country/region has in a year, usually to plan working days) and explicit exclusions (school holidays, non-day-off religious observances, company closures, stock exchange calendars). The final sentence routes the agent away from a plausible wrong use case.

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