Skip to main content
Glama

CheckMyTax NZ: New Zealand Tax Calculators

nz_public_holidays

Public holidays and business days (New Zealand) [NZ]. Lists New Zealand public holidays and regional anniversary days for 2026 and 2027, checks whether a date is a business day, adds or subtracts business days, and counts business days between two dates (Monday to Friday, excluding public holidays). Mondayised holidays count by default; pass includeMondayised false for people who work weekends. Only 2026 and 2027 are supported; other years return an error.

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": {
      "mode": "<mode>"
    },
    "name": "nz_public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNobusiness_days_between: end date (counted)
dateNois_business_day, add_business_days: the date
daysNoadd_business_days: whole business days to add (negative to go back)
modeYeslist: public holidays in a year; is_business_day: is a date a working day; add_business_days: move a date forward or back by business days; business_days_between: count business days after start up to and including end
yearNolist: calendar year
startNobusiness_days_between: start date (not counted)
regionNoOptional NZ anniversary region to include its anniversary day
extraHolidaysNoExtra non-working dates, e.g. a shutdown
includeRegionalNoAU: count regional holidays such as show days; default false
includeMondayisedNoNZ: count Mondayised holidays; default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the substantive behaviors: business days are Monday–Friday excluding public holidays, Mondayised holidays count by default, and unsupported years return an error. It does not describe the shape of the returned data, which matters somewhat for a tool with 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?

Purpose and scope are front-loaded, followed by the mode inventory, then defaults, then the hard year limitation. Every sentence adds information an agent needs; there is no filler or restatement of the name.

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 ten-parameter, four-mode tool with no output schema, the description covers the critical constraints (year range, business-day definition, Mondayisation default, error on out-of-range years). The remaining gaps are the undocumented `extraHolidays`/`includeRegional` parameters and the absence of any indication of what a `list` call returns.

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 100%, so the baseline is 3; the description earns above that by explaining the real-world meaning of includeMondayised (weekend workers) and the inclusive/exclusive convention of the business-day arithmetic. It says nothing about `extraHolidays` or `includeRegional`, so it does not fully cover all ten parameters.

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 description names the resource (New Zealand public holidays and business days) and enumerates all four operations — list holidays, is_business_day check, add/subtract business days, and business_days_between — which map one-to-one onto the `mode` enum. An agent can tell exactly what the tool does and that it is the NZ counterpart to au_public_holidays without opening the 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?

It gives concrete selection context: use includeMondayised=false for people who work weekends, and only 2026/2027 are valid years. It stops short of naming when to prefer a sibling (e.g., au_public_holidays for Australian dates) or how the modes differ in cost, but the guidance for the main configuration decision is explicit.

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