Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

nz_tax_code

Tax code (New Zealand) [NZ]. Picks the NZ tax code to put on an IR330 for a job (M, ME, SB, S, SH, ST, SA, CAE, EDW, NSW, with SL for a student loan), following IRD's rules for the common cases, and explains why. Doesn't calculate tailored tax codes or contractor (schedular) rates.

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": {
      "isMainIncome": "<isMainIncome>",
      "totalAnnualIncome": "<totalAnnualIncome>"
    },
    "name": "nz_tax_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoNZ tax year, e.g. "2026-27". Supported: 2026-27.
specialJobNo
isMainIncomeYesIs this job your main or highest-paying income?
nzTaxResidentNo
hasStudentLoanNo
totalAnnualIncomeYesEstimated total yearly income from all sources, before tax
mainJobAnnualIncomeNoWith several jobs: what the main job alone pays per year
receivesSuperOrBenefitNoNZ Super, a veteran's pension, a main benefit or an overseas equivalent
receivesWorkingForFamiliesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 disclose meaningful boundaries: it only handles IRD's common cases, and it explicitly refuses tailored codes and contractor rates. It also signals the response includes reasoning ('explains why'), which is useful given there is no output schema. It does not say what the return object looks like beyond that or confirm the tool is purely informational.

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?

Front-loaded with the resource and verb, then the output codes, then the limits. The code enumeration is long but genuinely informative rather than filler. Slightly dense as a single paragraph, but no sentence is wasted.

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 9-parameter advisory tool with no output schema, the description covers purpose and exclusions well but leaves the agent guessing about several inputs that materially affect the answer. An agent could call it, but not confidently predict or explain the result for non-default cases like residency, benefits, or special job types.

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 56%, below the 80% baseline, so the description should be compensating more than it does. It hints at the student-loan input via the 'SL for a student loan' mention, but says nothing about nzTaxResident, receivesSuperOrBenefit, receivesWorkingForFamilies, specialJob, or mainJobAnnualIncome and how they shift the result.

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 (picks the NZ tax code), the concrete artifact it feeds (the IR330 for a job), and enumerates the exact output set (M, ME, SB, S, SH, ST, SA, CAE, EDW, NSW, plus SL). That is enough to distinguish it from the surrounding levy/GST/kiwisaver calculators without opening a schema.

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?

Gives a clear operating context (choosing a tax code for a job's IR330 under IRD's rules for common cases) and explicit exclusions: no tailored tax codes, no contractor/schedular rates. It stops short of naming the sibling or tool an agent should reach for when a tailored code or schedular rate is actually needed.

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