Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_import_duty_calculator

Estimate customs duty, GST and the Customs and MPI goods levy on goods sent or shipped to New Zealand.

Use for: 'import duty calculator nz', 'how much gst on imports nz',
'customs charges on a shipment', 'landed cost nz', 'do I pay duty on
goods from overseas', 'customs goods levy', 'is there duty under $1000'.

$1,000 OR LESS, CUSTOMS COLLECTS NOTHING (NZ Customs Service): no duty,
GST or levy unless the item or shipment is valued over NZ$1,000. The
international freight to New Zealand is NOT part of that value. An
overseas supplier may already have charged GST at checkout. Same-supplier
orders arriving the same day count as one shipment. Alcohol and tobacco
are charged whatever their value and are not covered by this tool.

NOT FOR LUGGAGE: goods in a traveller's baggage fall under the $700
traveller allowance and carry neither goods levy. Say so if asked.

Over $1,000: duty is on the goods value only, not the freight. GST is
charged on the goods, the freight and insurance, AND the duty. $1,500 of
goods with $150 freight at 5% duty is $75 duty and $258.75 GST.

The goods levy (from 1 April 2026, excluding GST) is $51.81 by air or
post ($7.24 Customs + $44.57 MPI) and $118.44 by sea ($73.87 + $44.57);
GST is added. By air the example pays $393.33 to Customs. A broker will
also charge for their services.

GIFTS are charged like other goods here; Customs sources disagree on a
gift over $1,000 (see not_modelled), so tell the user to confirm.

Values are in NZD; there is no currency conversion.

Args:
    goods_value: Customs value of the goods in NZD, excluding freight.
    freight_insurance: International freight and insurance in NZD.
    duty_rate_percent: Duty rate as a percentage, e.g. 5.
    transport: 'air', 'post' (air rate) or 'sea'. Default 'air'.
    levy_excl_gst: Override the goods levy, NZD excl GST. Omit for the register.

Returns:
    Whether Customs collects, duty, the GST base, GST, the levy with its
    GST, the total payable to Customs, the landed cost, the sources and
    what is not modelled.

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": {
      "goods_value": "<goods_value>"
    },
    "name": "nz_import_duty_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
transportNoair
goods_valueYes
levy_excl_gstNo
duty_rate_percentNo
freight_insuranceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the whole burden and does so: it states the NZ$1,000 collection threshold, that freight is excluded from dutiable value but included in the GST base, the exact levy amounts by transport mode, that GST is on top of the levy, that broker fees are extra, and that no currency conversion occurs. It also flags an unresolved gift edge case by pointing to 'not_modelled'.

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?

Purpose is front-loaded, followed by usage triggers, then rules, then args and returns in a logical order. The worked numeric examples ($1,500 goods at 5% duty, $393.33 air example) are long and only partly necessary, making the description denser than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter calculator with no annotations and no output schema, the description covers inputs, computation rules, edge cases, exclusions, and the return contents (whether Customs collects, duty, GST base, GST, levy, total, landed cost, sources, not-modelled). Nothing an agent needs to call it or explain results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the Args block is essential, and it documents all five parameters with meaning the schema lacks — notably that 'transport' accepts 'air', 'post' (air rate) or 'sea' with a default of 'air', which the schema's bare string type does not convey. It also clarifies goods_value excludes freight, that levy_excl_gst is an override to omit normally, and gives a duty_rate_percent example format.

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?

Opens with a specific verb and resource: 'Estimate customs duty, GST and the Customs and MPI goods levy on goods sent or shipped to New Zealand.' The scope (imports into NZ, not domestic GST) clearly separates it from siblings like nz_gst_calculator or nz_road_user_charges_calculator.

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

Usage Guidelines5/5

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

Provides an explicit 'Use for:' phrase list matching likely user queries, then names exclusions: alcohol and tobacco are not covered, traveller luggage falls under the $700 allowance, and gifts over $1,000 should be confirmed with the user. This is the when/when-not pattern at full strength.

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