Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_benefit_entitlement_calculator

Estimate a New Zealand main benefit, its abatement and the Accommodation Supplement that goes with it.

Use for: 'how much is jobseeker', 'sole parent support rate', 'supported
living payment amount', 'how much can I earn before my benefit is cut',
'accommodation supplement how much', 'winter energy payment'.

FOUR THINGS DECIDE THE ANSWER AND ONLY THE FIRST IS WIDELY KNOWN.

The base rate depends on the benefit and the living situation.

ABATEMENT IS NOT A DOLLAR FOR DOLLAR CUT. The first $160 a week of other
income is free. Above that a sole parent loses 30c in the dollar up to $250
and 70c after; everyone else loses 70c from the start. People routinely
believe every dollar earned is a dollar lost and turn down work on that
basis, so if someone is asking whether it is worth working, say the free
zone exists and how big it is.

THE ACCOMMODATION SUPPLEMENT IS 70% OF HOUSING COSTS ABOVE AN ENTRY
THRESHOLD, not 70% of the rent. The threshold is 25% of the base rate for
renters and boarders and 30% for owners, and only 62% of a board payment
counts as a housing cost at all. It is then capped by area, 1 being the
highest cost. Someone whose rent is below the threshold gets nothing.

The Winter Energy Payment runs 1 May to 1 October and is only paid while
some main benefit is still payable after abatement.

Rates are read from the published register, and rate_source says which
figure was used, when it was verified and when it next changes. Benefit
rates move every 1 April, so do not reuse an answer across that date.

THIS IS AN ESTIMATE OF PUBLISHED RATES, NOT AN ASSESSMENT. Entitlement also
depends on residency, relationship status, assets and obligations no
calculator sees. Say so rather than presenting it as a decision.

Args:
    benefit_type: Which main benefit is being received.
    situation: Living situation, which selects the weekly rate.
    weekly_income: Other gross weekly income before tax.
    accommodation_cost: Weekly rent, board or ownership cost.
    housing_type: rent, board or mortgage. Board counts at 62%.
    area: Accommodation Supplement area, 1 to 4. Area 1 is highest cost.
    children: Number of dependent children.
    winter: Whether the Winter Energy Payment period applies.

Returns:
    The weekly entitlement step by step: base rate, abatement, supplement
    with its cap and entry threshold, winter payment and the total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo
winterNo
childrenNo
situationNosingle_25
benefit_typeNojobseeker
housing_typeNorent
weekly_incomeNo
accommodation_costNo

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 fully carries the behavioral disclosure burden. It explains non-obvious calculation traits: the $160 abatement-free zone, the 70% Accommodation Supplement is based on costs above a threshold (not 70% of rent), the 62% board count, area-based caps, Winter Energy Payment conditions, April 1 rate changes, and the estimate-not-assessment caveat. This is exceptionally transparent.

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 long but well-structured, starting with a clear purpose, moving through use cases, key calculation factors, caveats, and finally parameter details. Nearly every sentence carries substantive guidance or prevents a common misconception, though a little redundancy exists (e.g., the free zone is mentioned twice), keeping it from a perfect conciseness score.

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?

The tool is complex with 8 parameters, no output schema, and no annotations, yet the description covers all invocation-relevant details: calculation steps, rate source and verification, seasonal changes, limitations, and return structure ('base rate, abatement, supplement with its cap and entry threshold, winter payment and the total'). Nothing needed to call or understand the result 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?

The schema has 0% description coverage, but the description's Args section gives meaningful semantics for all 8 parameters, including calling weekly_income 'other gross weekly income before tax,' noting housing_type 'Board counts at 62%,' and clarifying 'area: 1 being highest cost.' This fully compensates for the bare schema.

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 and resource: 'Estimate a New Zealand main benefit, its abatement and the Accommodation Supplement that goes with it.' It further distinguishes itself from the sibling calculators by naming the exact benefit scenarios and formula components, so an agent can clearly identify this tool.

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?

The description provides a concrete 'Use for' list with example user queries like 'how much is jobseeker' and 'accommodation supplement how much,' giving clear context for when to invoke it. However, it does not explicitly mention alternatives or when-not-to-use, such as directing tax-related questions to sibling calculators, so it stops short of the 5-level 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