Skip to main content
Glama

CheckMyTax NZ: New Zealand Tax Calculators

nz_kiwisaver

KiwiSaver contributions (New Zealand) [NZ]. Works out yearly KiwiSaver contributions for 2026-27: the employee contribution, the employer contribution after employer superannuation contribution tax (ESCT), and the government contribution (25c per $1 up to $260.72 for members earning $180,000 or less). Assumes a full year of eligibility; part-year proration, temporary rate reductions and fund returns aren't covered.

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": {
      "salary": "<salary>",
      "employeeRate": "<employeeRate>"
    },
    "name": "nz_kiwisaver"
  }
}

Input Schema

NameRequiredDescriptionDefault
salaryYesGross annual salary in NZD
employeeRateYesEmployee contribution rate as a decimal: 0.035, 0.04, 0.06, 0.08 or 0.1
employerRateNoEmployer rate as a decimal; defaults to the 3.5% minimum
eligibleForGovernmentContributionNoFalse if not eligible (e.g. living overseas); default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the tax treatment applied (ESCT on the employer contribution), the government contribution formula and cap ($260.72, $180,000 income threshold), and the modelling assumptions and omissions. It doesn't state explicitly that this is a pure, side-effect-free calculation with no external dependencies, which is the main remaining gap.

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?

Three sentences, front-loaded with the calculation and the year, then the outputs, then the scope limits. The parenthetical formula is compact and earns its place; a small amount of nested detail in the middle sentence slightly reduces scannability.

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?

There is no output schema, so the description must convey the return values, and it does by naming the three computed amounts. Combined with the stated assumptions and exclusions, an agent has enough to call it correctly; only the exact response shape (object vs. scalars, rounding) remains unspecified.

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 schema already defines all four parameters, and the baseline of 3 applies. The description does add indirect meaning – the $180,000 threshold contextualises eligibleForGovernmentContribution and the ESCT mention contextualises employerRate – but it doesn't clarify parameter behaviour such as how a custom employeeRate interacts with the government contribution cap.

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 uses a specific verb and resource ('Works out yearly KiwiSaver contributions for 2026-27') and enumerates the three outputs computed: employee contribution, employer contribution after ESCT, and government contribution. That detail makes it unmistakable against siblings such as nz_take_home or nz_acc_levy, which are different 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 negative guidance: 'Assumes a full year of eligibility; part-year proration, temporary rate reductions and fund returns aren't covered,' which tells the agent when the tool is not appropriate. It stops short of naming an alternative for those excluded cases (e.g. a take-home or manual calculation), so it is strong but not a full when/when-not/alternative specification.

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