Skip to main content
Glama

Calculate.co.nz NZ Calculators

by nz.co.calculate
OverviewDiscussionsAdmin

nz_final_pay_calculator

Work out a New Zealand final pay: leave payout, notice and redundancy.

Use for: 'what should my final pay be', 'how much annual leave am I owed
when I leave', 'I am resigning, what do they owe me', 'do I get 8% holiday
pay'.

ASK HOW LONG THEY WORKED THERE FIRST. It decides the whole calculation:

  - Under 12 months: no leave entitlement has vested, so the Holidays Act
    pays 8% of ALL gross earnings during the employment. Set
    service="under12" and pass gross_earnings_total. A leave balance
    showing in a payroll system is NOT what they are owed.
  - 12 months or more: unused leave is paid out at a daily rate. Set
    service="over12" and pass leave_balance_days.

Getting that branch wrong is the common mistake and it changes the answer
completely.

ALWAYS say what the total leaves out: ordinary wages for days actually
worked are paid on top at the usual rate, and every figure is GROSS. The
leave payout is then taxed as an extra pay, which is nz_lump_sum_tax_calculator.

New Zealand has NO statutory redundancy pay. If they ask what redundancy
they are entitled to, the answer is whatever their employment agreement
says, and nothing if it says nothing.

Args:
    annual_salary: Annual salary. Give this OR hourly_rate.
    hourly_rate: Hourly rate, used with hours_per_week.
    hours_per_week: Ordinary weekly hours, for an hourly rate.
    service: "over12" or "under12".
    leave_balance_days: Unused leave in DAYS, for over12.
    gross_earnings_total: All gross earned, required for under12.
    average_weekly_earnings: Optional. Leave is paid at the greater of this
        and ordinary weekly pay; pass it if their pay varied.
    notice_weeks: Weeks of notice paid in lieu.
    redundancy: Agreed redundancy from the employment agreement.

Returns:
    Leave payout with its working shown, notice pay, redundancy, the gross
    total, and an explicit list of what is excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceNoover12
redundancyNo
hourly_rateNo
notice_weeksNo
annual_salaryNo
hours_per_weekNo
leave_balance_daysNo
gross_earnings_totalNo
average_weekly_earningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden of disclosure. It delivers thoroughly: the under-12-months 8% rule, the warning that a payroll leave balance is NOT owed in that case, the note that every figure is GROSS, and the explicit statement of what is excluded from the total. It even describes the return contents. This is far beyond a typical description.

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?

The description is long but well-structured with clear sections: use-cases, critical first question, branch logic, shared cautions, legal context, args, and returns. The most important instruction ('ASK HOW LONG THEY WORKED THERE FIRST') is front-loaded. Every sentence earns its place; there is no filler or repetition.

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 complex 9-parameter calculator with no output schema and no annotations, this description is complete. It covers branch selection, parameter requirements, calculation logic, exclusions, gross-vs-net, tax routing, redundancy policy, and what the tool returns. An agent has everything needed to invoke it correctly in its intended situations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description's dedicated Args section documents all nine parameters, including units ('leave_balance_days: in DAYS'), mutual exclusivity ('Give this OR hourly_rate'), required conditions ('required for under12'), and optional use cases ('pass it if their pay varied'). This fully compensates for the absent schema-level documentation.

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 opens with a specific verb and resource: 'Work out a New Zealand final pay: leave payout, notice and redundancy.' It names concrete use-case phrases like 'what should my final pay be' and clearly distinguishes this tool from related siblings by pointing to nz_lump_sum_tax_calculator for the tax treatment. The scope is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance: 'Use for: ...' lists likely user phrasings, then instructs 'ASK HOW LONG THEY WORKED THERE FIRST. It decides the whole calculation.' It explains the two service branches and exactly which parameters to pass for each. It also names the alternative tool for tax ('which is nz_lump_sum_tax_calculator') and clarifies the no-statutory-redundancy rule. This leaves no ambiguity about when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Calculate.co.nz NZ Calculators toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources