Skip to main content
Glama

CheckMyTax NZ: New Zealand Tax Calculators

nz_acc_levy

ACC earners' levy (New Zealand) [NZ]. ACC earners' levy for 2026-27: 1.75% of earnings up to the maximum liable earnings of $156,641 (GST inclusive). For employees it is deducted through PAYE. Doesn't cover work levies, the self-employed minimum earnings, or part-year earnings.

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": {
      "earnings": "<earnings>"
    },
    "name": "nz_acc_levy"
  }
}

Input Schema

NameRequiredDescriptionDefault
earningsYesAnnual liable earnings in NZD (salary or self-employed income)

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?

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses the flat rate, the maximum liable earnings threshold (implying results saturate above that ceiling), the GST-inclusive basis, and the PAYE context. It omits what the return value actually is (an annual levy dollar figure) and rounding behavior, which keeps it from a 5.

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?

Front-loaded with the levy's identity, then rate, then cap, then scope exclusions in a single dense burst with zero filler. Every clause (rate, cap, GST treatment, PAYE, exclusions) carries decision-relevant information.

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 one-parameter pure calculator with no annotations and no output schema, the description supplies rate, cap, tax year, GST basis and coverage limits — enough to call it correctly. The only gap is that the shape of the returned figure is never stated, which a careful agent might want.

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% and the single 'earnings' parameter is fully documented as annual liable earnings in NZD, so the baseline is 3. The description adds the $156,641 cap, which tells the agent that inputs above the ceiling are truncated — useful, but it is the same fact already reflected in the behavioural context rather than parameter-specific syntax.

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?

Names the exact resource (ACC earners' levy, New Zealand, 2026-27 tax year) and pins it down with the rate (1.75%) and liable-earnings cap ($156,641), so an agent can tell it apart from nz_gst, nz_kiwisaver and other NZ siblings without opening any schema. The '[NZ]' tag plus the flat 'doesn't cover work levies' exclusion further sharpens the boundary.

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?

Explicitly states scope exclusions — work levies, self-employed minimum earnings, part-year earnings — which tells the agent when NOT to rely on this tool. It does not name a concrete alternative tool or say 'use this when computing an employee's PAYE deduction', so the routing guidance stops short of a 5.

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