Skip to main content
Glama

Get public holidays

well_get_public_holidays
Read-only

List the public holidays of a country for one year, from the open Nager.Date calendar (more than 100 countries). Use it whenever a date depends on a holiday: a due date that falls on one, a delivery or a payment delay in working days, an appointment, a trip or a shop that may be closed. Never answer a holiday date from memory: movable days such as Easter change every year.

Pass country (ISO 3166-1 alpha-2, "FR") and year.

Returns status "found" with holidays, in date order, each with date (YYYY-MM-DD), name (English), local_name, nationwide (false: only some regions observe it, listed in regions, so say which) and types ("public" is a day off; "bank", "school", "authorities", "optional" and "observance" are not a day off for everyone). Or status "refused" with refusal: "unsupported_country" (the calendar does not serve it), "not_found", "unavailable" or "malformed_input"; pass on message and never invent a date.

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>",
      "year": "<year>"
    },
    "name": "well_get_public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesThe calendar year, four digits.
countryYesThe country, as an ISO 3166-1 alpha-2 code.
workspace_idNoTarget workspace. Optional: this tool describes the token itself rather than one workspace's data, so omitting it returns the same answer.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
sourceNo
statusYes
messageNo
refusalNo
successYes
holidaysNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / source / enum
      Previous value: -[
      -  "fr_recherche_entreprises",
      -  "gb_companies_house",
      -  "us_sec_edgar",
      -  "eu_vies",
      -  "gb_hmrc",
      -  "fr_base_adresse_nationale",
      -  "us_census_geocoder",
      -  "nager_public_holidays",
      -  "fr_prix_des_carburants",
      -  "navitia_journeys"
      -]New value: +[
      +  "fr_recherche_entreprises",
      +  "gb_companies_house",
      +  "us_sec_edgar",
      +  "eu_vies",
      +  "gb_hmrc",
      +  "fr_base_adresse_nationale",
      +  "us_census_geocoder",
      +  "nager_public_holidays",
      +  "fr_prix_des_carburants",
      +  "navitia_journeys",
      +  "youtube_oembed",
      +  "fr_bodacc"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-source profile is covered. The description adds real value beyond that: it discloses the return envelope ('status' found/refused), the refusal reasons ('unsupported_country', 'not_found', 'unavailable', 'malformed_input'), and the meaning of 'nationwide' and 'types' values. It does not state rate limits, caching, or cost of the open-world call, so it is good but not fully complete.

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?

Front-loaded with purpose, then a usage rationale, then inputs, then the return contract and failure modes - a logical order with no filler sentences. The returns paragraph is dense, and part of it restates what the output schema already encodes, which keeps it from a 5.

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?

Covers the full call cycle for a genuinely complex tool: what to pass, what 'found' vs 'refused' mean, how to read 'nationwide' and 'types', and an instruction to propagate 'message' rather than invent a date. With an output schema present, the description need not enumerate fields further, and nothing an agent needs in order to 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 coverage is 100% and every parameter (including workspace_id, conversation_id, workspace_scope) already has a full description, so the baseline is 3. The description repeats the two required inputs and adds the format hint ('ISO 3166-1 alpha-2, "FR"') plus the year constraint, but that is largely duplicative of the schema's enum of country codes and 'four digits' note.

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 with scope: 'List the public holidays of a country for one year' from Nager.Date, and notes the 100+ country coverage. An agent knows exactly what the tool returns without opening the schema, and the scope ('one year', 'of a country') is precise enough to distinguish it from any calendar-event sibling.

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?

Gives explicit triggers ('a due date that falls on one, a delivery or a payment delay in working days, an appointment, a trip or a shop that may be closed') and an explicit prohibition ('Never answer a holiday date from memory: movable days such as Easter change every year'). That is a when-to-use plus a when-not-to-improvise rule, which is about as strong as guidance gets for this tool type.

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