Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_public_holidays_calculator

List New Zealand public holidays for a year, count them, and find the next one.

Use for: 'public holidays nz 2027', 'when is the next public holiday nz',
'how many public holidays in nz', 'is waitangi day mondayised', 'when is
matariki 2028', 'auckland anniversary day', 'nz stat holidays'.

THE COUNT IS NOT ALWAYS ELEVEN. Ten before Matariki began in 2022, twelve
in 2022 with the one-off Queen Elizabeth II Memorial Day, eleven since, plus
one for a region's anniversary day.

MONDAYISATION MOVES THE DAY OFF, NOT THE HOLIDAY. For someone who does not
work that weekend day, Christmas, Boxing Day, 1 and 2 January move from a
Saturday to the Monday and from a Sunday to the TUESDAY (so a Sunday
Christmas is Tuesday 27 and Boxing Day Monday 26). Waitangi Day and Anzac
Day move to the Monday, and only from 2014. Each holiday carries both actual_date and date (the
day off), with mondayised set when they differ.

TWO HOLIDAYS CAN SHARE A DAY. Anzac Day fell on Easter Monday in 2011 and is
Mondayised onto it in 2038. distinct_days_off counts the day once.

MATARIKI is gazetted, not calculated, and is listed only from 2022. The
gazetted dates run to 2052, which is the last year this covers.

REGIONAL ANNIVERSARY DAYS are given on the day OBSERVED, which is rarely
the anniversary: usually the Monday nearest it (Auckland 29 January was
observed Monday 26 January 2026), but Taranaki is the second Monday in
March, Southland Easter Tuesday, Canterbury Show Day Friday in November,
South Canterbury the fourth Monday in September, Hawke's Bay the Friday
before Labour Day and Marlborough the Monday after (Employment New
Zealand). Each regional entry carries actual_date (the anniversary) and
date (the day off). Available from 2010.

Args:
    year: Calendar year, 2000 to 2052. Defaults to the year of after, or
        the current year.
    region: Optional anniversary region key, for example auckland,
        wellington, canterbury, otago. Omit for national holidays only.
    after: Optional ISO date. Returns the next holiday strictly after it.

Returns:
    Every holiday with its actual and observed date, the national,
    regional and distinct day counts, and the next holiday when asked.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nz_public_holidays_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
afterNo
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so: it warns the count is not always eleven and explains why, details the mondayisation rule including the Saturday-to-Monday and Sunday-to-Tuesday distinction with a 2014 cutoff, notes two holidays can share a day, and states that Matariki is gazetted rather than calculated. It also discloses return field names (actual_date, date, mondayised, distinct_days_off), which is essential given there is no output schema.

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?

Although long, the length is earned: each paragraph covers a distinct rule an agent cannot infer (count variance, mondayisation, shared days, Matariki gazetting, regional observance), and the capability statement and usage triggers are front-loaded before the edge cases. Capitalised emphasis is heavier than necessary but the content is dense rather than padded.

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 no annotations, no output schema, 0% schema description coverage, and a genuinely complex domain of NZ holiday rules, the description supplies everything needed to call it correctly and to interpret the result, including the 2052 ceiling and the 2010 floor for regional data. The only residual ambiguity, exact region key strings, is minor relative to the rest of the disclosure.

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 description coverage is 0%, so the description must compensate, and it does: year is bounded 2000–2052 with a documented default chain (year of 'after', else current year), after is defined as strictly-after ISO date, and region is explained as an optional anniversary key with four examples. The gap is that only four region keys are illustrated while eight regions are discussed in the prose, and the exact key format (underscores vs spaces, e.g. 'hawkes_bay') is never specified, leaving an agent to guess valid values.

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?

Opens with a specific verb-plus-resource statement — 'List New Zealand public holidays for a year, count them, and find the next one' — that names all three capabilities in one line. An agent can distinguish this from siblings like nz_business_days_calculator or nz_annual_leave_calculator without opening any schema.

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?

The 'Use for:' block supplies concrete triggering queries ('when is the next public holiday nz', 'is waitangi day mondayised') that map directly to the three parameters. It does not explicitly name the sibling tools an agent should prefer instead when the real need is business-day counting or holiday pay, so the exclusion side is implied rather than stated.

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