site

New Zealand final pay and annual leave calculator

calculate

Run the New Zealand final pay and annual leave calculator calculator: Rate for unused annual holidays; Unused annual holidays; 8% of gross earnings; Final pay before tax. Missing inputs fall back to their documented defaults.

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": "calculate"
  }
}

Input Schema

Name	Required	Description	Default
`awe`	No	Average weekly earnings
`owp`	No	Ordinary weekly pay
`service`	No	How long had you worked there?	entitled
`noticePay`	No	Pay for the rest of the notice period
`wagesOwed`	No	Wages for hours worked but not yet paid
`leaveWeeks`	No	Unused annual holidays you are entitled to (weeks)
`alreadyPaid`	No	Holiday pay you have already had
`grossEarnings`	No	Gross earnings for the 8% payment
`publicHolidays`	No	Public and alternative holidays owed

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully notes that missing inputs fall back to documented defaults and lists the main output components, but it does not state that the calculation is non-mutating, describe rounding or currency assumptions, or explain the response format.

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?

The description is short and front-loads the core action. The semicolon-separated output list is efficient, though the repeated word in 'calculator calculator' is an avoidable blemish.

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 a nine-parameter calculator with no annotations and no output schema, the description is only moderately complete. It names several outputs and mentions defaults, but it does not explain the calculation logic, currency assumption, or full response shape, leaving gaps for an agent trying to interpret results.

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 100%, so the input schema already documents all nine parameters and their defaults. The description mentions default fallback behavior but does not add parameter-specific meaning, format details, or interaction rules beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: run the New Zealand final pay and annual leave calculator. It also lists the main computed components, making the tool's domain clear. However, it does not differentiate from the related sibling calculator_describe, and the repeated word 'calculator calculator' slightly muddies the statement.

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

Usage Guidelines2/5

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

The description implies when the tool is relevant by naming the New Zealand final pay and annual leave scenario, but it gives no explicit when-to-use guidance, no exclusions, and no reference to the sibling calculator_describe or other alternatives. An agent must infer usage from the domain alone.

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

All site tools Inspect

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

Need Help?