Skip to main content
Glama

Calculate.co.nz NZ Calculators

nz_rates_water_calculator

Estimate a New Zealand house's 2026/27 council rates and water charges.

Use for: 'how much are rates on a $700k house', 'council rates calculator
nz', 'auckland rates estimate', 'christchurch rates and water', 'what are
water rates in wellington', 'rates per week nz'.

ONLY NINE COUNCILS, each for a standard house in the area stated:
Auckland (Watercare-metered house), Wellington City, Christchurch City,
Hamilton City, Tauranga City, Dunedin City, Selwyn (Rolleston),
Waimakariri (Rangiora) and Queenstown Lakes (Queenstown). Any other council
or town (Kaiapoi, Wanaka, Upper Hutt, Nelson...) returns an error: tell the
user to use that council's own rates search. Never substitute another
council's figures.

FIGURES ARE EACH COUNCIL'S ADOPTED 2026/27 RATES, GST inclusive, with the
water organisation's 2026/27 prices where it bills water (Watercare, Tiaki
Wai, IAWAI, Selwyn Water). Usage matters only in Auckland, Tauranga,
Selwyn, and Christchurch above 900 litres a day (each part of a m3 charged
as a whole one). A usage of 0 is 0; null is the 170 m3 starting figure.
For Waimakariri pass land_value, or its urban drainage rate is left out
(land_value_rate_left_out says so).

Outside Auckland (a unitary council) regional council rates are NOT
included. Every answer carries source_url, rating_year and not_included.

Args:
    capital_value: The property's capital value in dollars.
    council: A council key or name from the page.
    water_usage_m3: Annual water use in cubic metres. Default 170.
    land_value: The property's land value; used only for Waimakariri.

Returns:
    General rate, UAGC, water, wastewater, stormwater, rubbish, other
    targeted rates, the total yearly, quarterly, monthly and weekly, rates
    as a share of CV, who bills water, the 2026/27 rebate figures, the
    rating year and the council's source.

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": {
      "capital_value": "<capital_value>"
    },
    "name": "nz_rates_water_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
councilNochristchurch
land_valueNo
capital_valueYes
water_usage_m3No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses that figures are each council's adopted 2026/27 rates, GST inclusive, with water organisation pricing where applicable. It explains usage-dependent behavior, the 0 versus null semantics, Waimakariri's land_value requirement, and that regional council rates are excluded outside Auckland. These are substantive behavioral details beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but appropriately structured for a multi-constraint calculator. It front-loads the purpose, then use cases, limitations, rates details, Args, and Returns. Every section contributes useful selection or invocation information, with no obvious filler.

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 four-parameter calculator with no annotations and no output schema, the description is complete enough to call correctly. It covers supported councils, parameter meanings, edge cases, included/excluded charges, and return fields. Nothing essential is missing for correct invocation.

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 description coverage is 0%, so the description must compensate and it does: capital_value is in dollars, council is a key or name from the listed councils, water_usage_m3 is annual cubic metres defaulting to 170 with special 0/null handling, and land_value is used only for Waimakariri. The Args section adds clear meaning beyond the bare input 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 states a specific verb and resource: estimate a New Zealand house's 2026/27 council rates and water charges. It clearly distinguishes the tool from sibling calculators by naming the exact domain and scope. An agent can identify this as the rates/water calculator without ambiguity.

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?

It gives explicit example queries and clearly limits use to nine named councils, stating that any other council or town returns an error and should be handled via that council's own rates search. It also warns never to substitute another council's figures. This is strong when-to-use and when-not-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