Skip to main content
Glama

CheckMyTax NZ: New Zealand Tax Calculators

nz_ietc

Independent earner tax credit (New Zealand) [NZ]. Works out the yearly NZ independent earner tax credit (IETC): the full amount between the lower and upper income limits, reducing above that, and nothing for people excluded by Working for Families, NZ Super or a benefit.

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": {
      "income": "<income>"
    },
    "name": "nz_ietc"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoNZ tax year, e.g. "2026-27". Supported: 2026-27.
incomeYesYearly income before tax
excludedNoYou or your partner get Working for Families, or you get NZ Super, a benefit or a similar pension
nzTaxResidentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 disclose the calculation behavior: full entitlement inside the band, abatement above the upper limit, and zero for the excluded groups. It does not state the return shape (a credit amount in NZD?), nor that only the 2026-27 year is supported, nor the role of residency in eligibility, leaving real behavioral gaps.

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?

A single dense sentence with the resource named first and the computation logic trailing; every clause carries information. Slightly over-packed with parenthetical exclusions, but no filler.

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 4-parameter calculator with no output schema, the definition covers eligibility and the band structure but leaves the return value and the residency/year handling unexplained. An agent could call it, yet would be guessing what comes back and whether the year matters.

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 75%, so most parameters are already documented. The description reinforces the 'excluded' semantics (Working for Families, NZ Super, a benefit) and explains how income drives the abatement, but adds nothing about the undocumented nzTaxResident parameter or the year constraint.

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 names a specific verb-level outcome (works out the yearly NZ independent earner tax credit) and pins down the domain and scope. It is clearly distinct from the surrounding GST/levy/pay calculators by resource, though it never names an alternative tool.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the IETC calculator, but there is no statement of when to reach for it over nz_take_home or nz_tax_code, and no prerequisites such as residency being required. The scope sentence ('full amount between the lower and upper income limits, reducing above that') gives useful framing but is not when-to-use guidance.

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