Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_citizenship_calculator

Check the presence-day test for New Zealand citizenship by grant.

Use for: 'how many days do I need in NZ for citizenship', 'NZ citizenship
eligibility', '1350 days citizenship', '240 days rule NZ citizenship',
'can I apply for NZ citizenship yet', 'citizenship presence calculator'.

BOTH TESTS MUST PASS, AND NEITHER RESCUES THE OTHER. Over the five years
immediately before applying (Citizenship Act 1977 s8(2)(b)): at least
1,350 days in New Zealand in total, AND at least 240 days in each of the
five years. A comfortable total of 1,410 still fails if one 12-month
period was 230. Five bare minimums of 240 total only 1,200, which fails
the total. Lead with whichever test failed and by how much.

ONLY DAYS ENTITLED TO BE IN NZ INDEFINITELY COUNT: for example on a
resident or permanent resident visa, as an Australian citizen, or as an NZ
citizen by descent (DIA Guidance 1(a)). Time on a work, student or visitor
visa does not count towards either test. DIA has confirmed in writing
(reply to data.govt.nz dataset request 847, 18 September 2023) that the
days you leave and arrive in New Zealand both count as days in New
Zealand.

A "YEAR" IS A 12-MONTH PERIOD COUNTED BACK FROM THE DATE DIA RECEIVES THE
COMPLETED APPLICATION AND FEE, not a calendar year. All five periods move
with that date, so a later date can pass where today fails, but it needs
a fresh count of all five, not just a low period falling away.

This is eligibility guidance only. Applications are decided by the
Minister of Internal Affairs, or by the Department of Internal Affairs
under delegated authority, who also assess DIA's six other requirements:
entitlement to reside indefinitely, good character, knowledge of the
responsibilities and privileges of citizenship, English language,
intention to reside and full capacity (in other_requirements).

Args:
    days_per_year: Five day counts, MOST RECENT FIRST (months 1 to 12
        before applying, then 13 to 24, ... 49 to 60). Each a whole
        number, 0 to 366.

Returns:
    Whether the presence requirement is met, the total against 1,350, each
    period against 240 with its margin, the number of periods below 240,
    the page's plain-language verdict and explanation, and DIA's seven
    requirements.

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": {
      "days_per_year": "<days_per_year>"
    },
    "name": "nz_citizenship_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
days_per_yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses rich behavioral detail: both tests must pass independently, only days with indefinite entitlement count (work/student/visitor visas excluded), leaving and arriving days both count, and a 'year' is defined by DIA's receipt date. It also notes the tool is guidance-only and that DIA assesses six other requirements.

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?

The description is front-loaded with the core rule and uses clear sections (Use for, BOTH TESTS, ONLY DAYS, A 'YEAR', Returns). It is dense but every sentence carries legal or operational weight; slightly long but justified by the complexity of the domain.

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?

Given a single-parameter tool with no output schema and no annotations, the description fully covers input format, output content (total vs 1,350, each period vs 240 with margin, plain-language verdict), and legal nuances. An agent has everything needed to invoke and interpret results correctly.

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 description must compensate entirely for the sole parameter. It does so thoroughly: days_per_year is five whole numbers (0–366), most recent first, mapping months 1–12, 13–24, etc., with a concrete example of ordering.

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?

The description opens with a specific verb+resource: 'Check the presence-day test for New Zealand citizenship by grant.' It names the exact legal test (presence-day) and distinguishes it from the many other NZ calculators in the sibling list, which cover unrelated domains like tax, leave, and benefits.

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?

It provides explicit example queries ('how many days do I need in NZ for citizenship', '1350 days citizenship') and clarifies the tool is 'eligibility guidance only', pointing to DIA for final decisions. It does not explicitly state when not to use the tool, but no sibling alternative exists, so guidance is effectively clear.

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