Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_business_days_calculator

Count New Zealand working days between two dates, or add or subtract N working days.

Use for: 'working days between two dates nz', '10 working days from today
nz', 'business days calculator nz', 'how many working days until
christmas', '20 working days notice', 'subtract working days from a date'.

THE END DATE IS COUNTED, THE START DATE IS NOT, unless include_start is
true. Monday to Friday of one week is 4 business days by default.

ADD AND SUBTRACT start from the next (or previous) day, so one business day
after a Friday is the Monday.

HOLIDAYS COME OUT ON THEIR OBSERVED DATES. A Saturday Anzac Day removes the
Monday after it; Christmas and Boxing Day on a weekend remove the Monday and
Tuesday. Waitangi Day and Anzac Day were only Mondayised from 2014, and
Matariki exists only from 2022. A holiday on the weekend itself counts as a
weekend day.

A REGIONAL ANNIVERSARY DAY is excluded only when region is given, on the
day it is OBSERVED that year, by Employment New Zealand's rules: usually
the Monday nearest the anniversary (Auckland 29 Jan observed Monday 26
January 2026), with exceptions such as Southland on Easter Tuesday and
Canterbury on Show Day Friday in November. Available from 2010.

Statutes often define working days with their own extra exclusions, such
as 25 December to 15 January. This does not apply those.

Args:
    start_date: ISO date, YYYY-MM-DD.
    end_date: ISO date, for mode between. Counted.
    mode: between, add or subtract.
    days: Business days to add or subtract, at least 1.
    include_start: Whether the start date itself counts. Default False.
    region: Optional anniversary region key, for example auckland,
        wellington, canterbury.

Returns:
    Business, calendar, weekend and holiday counts, the holidays met, the
    target date for add or subtract, and weeks and days.

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": {
      "start_date": "<start_date>"
    },
    "name": "nz_business_days_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
modeNobetween
regionNo
end_dateNo
start_dateYes
include_startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the whole behavioral load, and it does substantial work: inclusive/exclusive endpoint rules, add/subtract offsetting from the adjacent day, observed-date holiday logic, Mondayisation only from 2014, Matariki only from 2022, and regional anniversaries only from 2010. The remaining gap is that it never states how the tool handles invalid or contradictory input (e.g. end_date before start_date, or days supplied in 'between' mode).

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?

Capitalised lead-ins front-load the non-obvious rules (endpoint counting, offset direction, observed holidays, regional anniversaries) and the Args/Returns block is scannable. The query-phrase list is longer than strictly needed and mildly padding, keeping 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?

For a six-parameter date calculator with no annotations and no output schema, the description covers the counting convention, holiday and anniversary edge cases, historical cutoffs, documented limitations, and the shape of the return values. An agent has enough to call this correctly and interpret the result.

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 0%, so the description's per-parameter notes do real work, giving the accepted mode values, the ISO date format, the minimum of 1 for days, the default for include_start, and example region keys. However, it does not resolve ambiguity around which parameters are ignored in each mode, so it adds meaning without fully closing a zero-coverage schema.

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?

The opening sentence gives a specific verb and resource plus the two operating modes: count working days between dates, or add/subtract N working days. It is clearly separable from the sibling nz_public_holidays_calculator, which would list holidays rather than compute differences.

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?

A 'Use for' list of realistic query phrasings makes the intended cases concrete, and the closing note explicitly excludes statute-specific extra exclusions (e.g. 25 Dec to 15 Jan), telling the agent when this tool is not sufficient. It does not name a sibling alternative for those statute cases, so it falls short of a full when/when-not/alternative triad.

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