Skip to main content
Glama

Lookup: India PIN codes and districts, public holidays

Public holidays on a date or in a year

holidays_on
Read-onlyIdempotent

Public holidays for the US (federal), GB (England and Wales, Scotland, Northern Ireland), AU (states and territories) or CA (federal and provinces) for 2026 to 2028. Give a date (YYYY-MM-DD) or a year, and optionally a region such as NSW, Scotland or ON. A date also matches a holiday's legal date (flagged match "legal_date") when the day off is observed on another day. Not every region has every year: a region-year with no data returns status no_data, not "no holiday". Sources: US OPM, GOV.UK (OGL v3.0), Australian and Canadian government pages named in each row.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD
yearNoYYYY
regionNoOptional region, e.g. NSW, Scotland, ON.
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses genuinely non-obvious behavior: a date can match a holiday's legal date when the day off is observed elsewhere (flagged match "legal_date"), and an uncovered region-year returns status no_data rather than an empty result. It also pins the supported year window and names the authoritative sources per country.

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 scope, then usage mechanics, then the two behavioral caveats, then provenance -- a sensible ordering with no redundant sentences. The source-attribution tail is defensible for a data-provenance tool but is the least essential part.

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?

With no output schema, the description carries return-value burden and does a good job explaining the no_data status and the legal_date match flag. Country-to-region granularity is described but not fully enumerated, which is a minor gap for a 4-parameter lookup tool with annotations covering safety.

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?

Schema coverage is 75%, and the description adds real meaning: concrete region examples (NSW, Scotland, ON) tied to the country dimension, the YYYY-MM-DD date format, and the fact that region is optional. It does not clarify what happens if both date and year are supplied, leaving one ambiguity.

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 resource precisely (public holidays) and enumerates the exact scope: US federal, GB constituent nations, AU states/territories, CA federal and provinces, limited to 2026-2028. An agent immediately knows what it retrieves. It does not name the sibling next_holiday to differentiate, so it stops short of a 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?

It clearly states the invocation contract -- supply a date (YYYY-MM-DD) or a year, plus an optional region -- which tells the agent the conditions under which this tool applies. It gives no explicit when-not guidance or sibling alternative (e.g. next_holiday for 'what's the next holiday'), so it is clear context without exclusions.

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