Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

nz_take_home

Take-home pay (New Zealand) [NZ]. Works out yearly take-home pay for one main NZ job: income tax, ACC earners' levy, KiwiSaver, student loan and the independent earner tax credit, plus effective and marginal rates and the likely tax code. Divide by 52, 26 or 12 for per-pay figures. Doesn't handle secondary jobs, tailored tax codes, non-residents or the temporary 3% KiwiSaver rate.

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": {
      "annualGross": "<annualGross>"
    },
    "name": "nz_take_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoNZ tax year, e.g. "2026-27". Supported: 2026-27.
claimIetcNoClaim the independent earner tax credit through the ME code, if eligible
annualGrossYesGross annual salary or wages before tax, from one main job
kiwisaverRateNoEmployee KiwiSaver rate as a decimal, e.g. 0.035; 0 if not in KiwiSaver
hasStudentLoanNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 lists the exact deductions applied, discloses that it only computes annual figures with manual division for per-pay amounts, and names four unsupported scenarios. It stops short of saying whether results are estimates, what rounding applies, or the shape of the returned object (no output schema exists), which leaves a residual gap.

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?

Two dense sentences with zero filler: the first states what is computed and what is returned, the second covers the per-pay conversion and the exclusions. Front-loaded and every clause earns its place.

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 five-parameter composite calculator with no output schema and no annotations, the description supplies the computation model, the limitation set, and a partial list of return values. It could be stronger by specifying how KiwiSaver rates default or what the tax-code output depends on, but an agent has enough to call it correctly.

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 coverage is 80%, with year, annualGross and claimIetc already documented in the schema (including the 'Supported: 2026-27' note). The description adds little param-level meaning beyond reinforcing that annualGross is from a single main job and implying KiwiSaver/IETC are factored into the calculation; the undocumented hasStudentLoan and kiwisaverRate semantics are left to the schema alone.

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?

States a specific verb and resource ('works out yearly take-home pay') and enumerates exactly which components are included (income tax, ACC earners' levy, KiwiSaver, student loan, IETC) and which derived figures come back (effective/marginal rates, likely tax code). This clearly distinguishes it from the single-component siblings such as nz_acc_levy, nz_kiwisaver, nz_ietc and nz_tax_code, since this tool is the composite calculator.

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?

Scopes usage tightly to 'one main NZ job' and explicitly excludes secondary jobs, tailored tax codes, non-residents and the temporary 3% KiwiSaver rate, which is genuine when-not guidance. It does not, however, name which sibling to reach for in those excluded cases (e.g. nz_tax_code for secondary jobs), so the routing is implied rather than 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