Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_holiday_pay_calculator

Work out New Zealand holiday pay: annual leave, 8% pay as you go, public holidays, or the leave payout on termination.

Use for: 'how is holiday pay calculated NZ', 'holiday pay calculator',
'average weekly earnings vs ordinary weekly pay', '8% holiday pay casual',
'pay as you go holiday pay', 'do I get time and a half on a public holiday',
'alternative holiday day in lieu', 'holiday pay when I leave my job'.

PICK THE MODE. Each has one rule that is regularly got wrong.

annual_leave: leave is paid at the GREATER of ordinary weekly pay and
average weekly earnings (1/52 of the gross earnings for the 12 months
before the last pay period before the holiday). Someone whose overtime or
commission lifts their average above their base is owed the average.

pay_as_you_go: 8% of gross pay BEFORE the loading. $1,200 earns $96, so the
pay is $1,296; 8% of $1,296 is the wrong base. Lawful only for a fixed term
under twelve months or genuinely intermittent or irregular work, written
into the agreement and an identifiable part of each pay. payg_allowed says
whether it is; the loading is shown either way. Pass pay_periods_per_year
(26 fortnightly, 12 monthly) for the annual figure.

public_holiday: worked, at least time and a half for the hours, PLUS an
alternative holiday (a paid day off later) if it was an otherwise working
day. Time and a half is on everything they would have been paid for those
hours; hourly_rate is taken as that. A day the employee would not
otherwise have worked earns the time and a half only. Not worked on an
otherwise working day: relevant daily pay (hourly_rate x normal_hours), or
average daily pay (daily_pay_method="average" with
days_worked_last_52_weeks) where relevant daily pay cannot practicably be
worked out or varies. Alternative holidays do not expire; after 12 months
the employee may ask to exchange one for payment.

termination: ask whether they worked there 12 months. Over 12 months, the
untaken ENTITLEMENT from completed years (untaken_weeks: not a payslip
balance that includes leave accruing since the anniversary) at the
greater of the two weekly rates, plus 8% of gross earnings since the last
anniversary, less holiday_pay_already_paid; those earnings INCLUDE the
leave paid out and any public holidays (public_holidays_in_leave_period,
s40) and alternative holidays (alternative_holidays_owed) paid out, and
earnings_since_anniversary should include final wages, notice pay and
any bonus or commission. Under 12 months, service="under12": 8% of the
earnings since they started. Same code as nz_final_pay_calculator, so the
two agree.

This is the Holidays Act 2003, which applies until the Employment Leave Act
2026 commences on 6 August 2028 (State school board staff on the education
payroll: by Order in Council, no later than 6 August 2036). All figures are
gross. Rules from the Act and Employment New Zealand.

Args:
    mode: annual_leave, pay_as_you_go, public_holiday or termination.
    ordinary_weekly_pay: What a normal week earns.
    gross_earnings_last_52_weeks: 12 months of gross earnings, for AWE and
        average daily pay.
    leave_weeks: Weeks of leave taken (annual_leave).
    gross_pay_period: Gross pay before the 8% loading (pay_as_you_go).
    employment_type: casual-genuine, casual-doubtful, fixed-term-under,
        fixed-term-over or permanent (pay_as_you_go).
    in_agreement: 8% PAYG is in the written agreement.
    payslip_identified: The 8% is an identifiable part of the pay.
    pay_periods_per_year: Pay periods a year for the annual figure.
    worked: The public holiday was worked.
    otherwise_working_day: The day would otherwise have been worked.
    hours_worked: Hours worked on the public holiday.
    hourly_rate: Ordinary hourly rate.
    normal_hours: Hours they would have worked that day.
    multiplier: Public holiday rate, at least 1.5.
    public_holiday_days: Public holidays not worked.
    daily_pay_method: auto, relevant or average.
    days_worked_last_52_weeks: Days worked or on paid leave, for average
        daily pay.
    service: over12 or under12 (termination).
    untaken_weeks: Untaken entitlement from completed years, in weeks
        (termination).
    earnings_since_anniversary: Earnings since the last anniversary,
        including final wages (termination).
    public_holidays_in_leave_period: s40 public holidays (termination).
    alternative_holidays_owed: Alternative holidays not taken
        (termination).
    holiday_pay_already_paid: Holiday pay already paid in advance or as
        pay as you go (termination).

Returns:
    total_gross for the mode, the working spelled out, the OWP and AWE
    comparison where it applies, PAYG eligibility, the daily rate and its
    basis, the alternative holiday, and the termination split.

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_holiday_pay_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoannual_leave
workedNo
serviceNoover12
multiplierNo
hourly_rateNo
leave_weeksNo
hours_workedNo
in_agreementNo
normal_hoursNo
untaken_weeksNo
employment_typeNocasual-genuine
daily_pay_methodNoauto
gross_pay_periodNo
payslip_identifiedNo
ordinary_weekly_payNo
public_holiday_daysNo
pay_periods_per_yearNo
otherwise_working_dayNo
holiday_pay_already_paidNo
alternative_holidays_owedNo
days_worked_last_52_weeksNo
earnings_since_anniversaryNo
gross_earnings_last_52_weeksNo
public_holidays_in_leave_periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so unusually well: it states the legal basis (Holidays Act 2003) and its sunset dates, that all figures are gross, that PAYG legality is checked and reported via payg_allowed, that the loading is shown either way, and that alternative holidays never expire. It stops short of stating that this is a pure side-effect-free computation, and it never warns that all 24 parameters are optional with defaults, so a zero-argument call silently computes a meaningless annual_leave result.

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 structure is good — purpose, then use cases, then mode rules, then Args, then Returns — with headings that let an agent skim. But it is very long for a calculator, and the mode prose mixes statutory rationale (day-in-lieu exchange after 12 months, s40 references) with invocation guidance, while the Args block duplicates ground already covered in the mode sections. Some trimming was possible without losing callable 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 24-parameter, four-mode statutory calculator with no annotations, no output schema and no schema descriptions, this is close to complete: it supplies parameter meanings, legal basis, per-mode edge rules and a 'Returns:' summary describing what comes back. The remaining gap is operational — how to behave when mode is omitted or when parameters from a different mode are supplied — which matters given every parameter has a default.

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 carry everything — and it does document all 24 parameters, including the enumerated value sets for mode, employment_type, daily_pay_method and service that the schema itself omits. Several entries add real disambiguation ('untaken_weeks: not a payslip balance that includes leave accruing since the anniversary'; 'gross_pay_period: Gross pay before the 8% loading'), but others are bare restatements ('worked: The public holiday was worked'; 'hourly_rate: Ordinary hourly rate'), and several public-holiday-only parameters (multiplier, normal_hours, public_holiday_days) are not tagged with the mode that consumes them.

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+resource pairing ('Work out New Zealand holiday pay') and immediately enumerates the four computations covered: annual leave, 8% PAYG, public holidays, termination payout. It distinguishes itself from the crowded NZ calculator sibling set, and explicitly notes the overlap with nz_final_pay_calculator, so an agent knows exactly what domain this tool owns.

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 lists concrete user phrasings that map to this tool, and 'PICK THE MODE' tells the agent how to route within the tool, including the discriminating rule for each mode (e.g. PAYG only for fixed term under 12 months or genuinely intermittent work). What it does not do is tell the agent when to prefer the sibling nz_annual_leave_calculator or nz_final_pay_calculator over the corresponding mode here — it only says the code agrees, not which entry point to pick.

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