Skip to main content
Glama

CheckMyTax NZ: New Zealand Tax Calculators

nz_holiday_pay

Holiday pay (New Zealand) [NZ]. Works out New Zealand holiday pay under the Holidays Act 2003: annual holidays (greater of ordinary weekly pay and average weekly earnings), 8% pay-as-you-go, public holiday pay (time and a half plus an alternative holiday if worked) and holiday pay on finishing a job. Doesn't handle sick or bereavement leave, variable-pay weeks, employer-specific agreements or the Employment Leave Act (due August 2028).

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": {
      "type": "<type>"
    },
    "name": "nz_holiday_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesannual: pay for annual holidays taken; payg: 8% pay-as-you-go; public_holiday: pay for a public holiday; final_pay: holiday pay on finishing a job
grossNopayg: gross pay for the period
workedNopublic_holiday: whether they worked the public holiday
weeksTakenNoannual: weeks of annual holidays taken; defaults to 4
alreadyPaidNofinal_pay: holiday pay already paid in advance or as pay-as-you-go
weeksEmployedNoannual, final_pay: weeks employed if under 52; defaults to 52
relevantDailyPayNopublic_holiday: what the employee would have earned for the day, including regular allowances
ordinaryWeeklyPayNoannual, final_pay: gross pay for a normal week, excluding bonuses and employer super
entitledWeeksOwingNofinal_pay: weeks of annual holidays entitled to but not taken
grossEarnings12MonthsNoannual, final_pay: gross earnings in the 12 months before the end of the last pay period
grossSinceAnniversaryNofinal_pay: gross earnings since the last annual holidays anniversary date

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 well: it discloses the legal framework, the formulas for each mode, and the main exclusions. It does not explain the return value or error behavior, which leaves a gap for a calculator 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?

It is a single dense paragraph with the scope, modes, and exclusions front-loaded. Every sentence adds substantive information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter calculation tool with no output schema, the definition covers scope and formulas well but never says what the tool returns. An agent can invoke it correctly, but cannot know whether to expect a numeric amount, a breakdown, or an alternative-holiday entitlement.

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 baseline is 3. The description adds meaningful calculation semantics beyond the schema, such as annual holidays using the greater of ordinary weekly pay and average weekly earnings, and public holiday pay including time and a half plus an alternative holiday if worked.

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 states a specific verb and resource: it works out New Zealand holiday pay under the Holidays Act 2003. It enumerates the four supported calculation modes (annual, pay-as-you-go, public holiday, final pay), so an agent can distinguish this from sibling calculators.

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 clear scope and explicit exclusions: sick leave, bereavement leave, variable-pay weeks, employer-specific agreements, and the future Employment Leave Act. It does not name alternative tools, but the when-not guidance is unusually specific.

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