Skip to main content
Glama
Sign In

Calculate.co.nz NZ Calculators

by nz.co.calculate
OverviewDiscussionsAdmin

nz_standard_drinks_calculator

Count the New Zealand standard drinks in a drink, with grams of pure alcohol and calories from the alcohol.

Use for: 'how many standard drinks in a bottle of wine', 'standard drinks
calculator nz', 'how many standard drinks in a beer', 'standard drinks in a
can of rtd', 'what is a standard drink nz', 'standard drinks in a shot'.

ONE NZ STANDARD DRINK IS 10 GRAMS OF PURE ALCOHOL: volume (mL) x ABV / 100
x 0.789 (the density of ethanol) / 10. A 330 mL can at 5% is 1.3 standard
drinks, so a six-pack is nearly eight, and a 750 mL bottle of wine at 13% is
7.7.

THE SIZE IS NATIONAL. A UK unit is 8 g and a US drink 14 g; this counts the
New Zealand drink only.

ABV IS A PERCENTAGE: 5 for 5%, 40 for 40%. Values between 0 and 0.5 are
refused as likely fractions.

THIS DOES NOT ESTIMATE BLOOD OR BREATH ALCOHOL and never says anyone is
safe, sober or fit to drive. Do not use it to answer whether someone can
drive.

THE LIMITS DIFFER BY SEX. Health New Zealand Te Whatu Ora's low-risk
drinking advice: women no more than 2 standard drinks a day, 10 a week and
4 at a time; men no more than 3 a day, 15 a week and 5 at a time; everyone
at least 2 alcohol-free days each week. Lower-risk is not no risk. Do not
drink if pregnant, planning to get pregnant or breastfeeding; under 18; on
medication that interacts with alcohol or with a condition made worse by
drinking; unwell, depressed, tired or cold; or about to operate machinery
or a vehicle or do anything risky. Never give one set of limits for
everyone.

Calories are kilocalories: 29 kJ per gram of alcohol / 4.18 (Food
Standards Code Schedule 11), about 6.94 per gram.

Args:
    volume_ml: Volume of one drink in millilitres.
    abv_percent: Alcohol by volume as a percentage, 5 for 5%.
    quantity: How many of that drink, a whole number of at least 1.
    preset: beer_330, beer_440, beer_500, craft_330, wine_150, wine_250,
        wine_bottle, spirit_30, spirit_45, rtd_330 or cider_330.
    limits_for: "women" (default) or "men": whose limits to compare with.

Returns:
    Standard drinks (as the page shows them, and to two places), grams of alcohol, alcohol
    calories, the limits applied, the share of the weekly and at-a-time
    limits, and whether the total is within the at-a-time and daily limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nz_standard_drinks_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNo
quantityNo
volume_mlNo
limits_forNowomen
abv_percentNo

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 supplied, the description carries the full burden and does so: it discloses the exact computation (volume x ABV/100 x 0.789 / 10), the input-rejection rule (ABV between 0 and 0.5 refused as a likely fraction), what the response contains, and the safety boundary that it never asserts anyone is safe or fit to drive.

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

Conciseness3/5

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

It is front-loaded and clearly sectioned (purpose, use cases, formula, national scope, ABV rule, exclusions, limits, calories, Args, Returns). However it is substantially longer than needed for tool selection: the detailed weekly/at-a-time limits per sex and the pregnancy/medication/under-18 advisory list go well beyond what an agent needs to decide to call it, even though the limits are echoed in the return value.

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 output schema the description supplies everything needed: input semantics, the calculation itself, unit nationalisation, safety exclusions, and a precise enumeration of return fields (standard drinks rounded two ways, grams, calories, applied limits, share of limits, in-limit flags).

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

Parameters4/5

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

Schema description coverage is 0% and has no enums, so the description must compensate, which it largely does: it defines volume_ml, abv_percent (percent not fraction, with the 0-0.5 guard), quantity (whole number >= 1), the full preset vocabulary, and limits_for with its 'women' default. The one unresolved ambiguity is precedence when both 'preset' and explicit volume_ml/abv_percent are supplied.

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 and resource ('Count the New Zealand standard drinks in a drink') and adds what else is returned (grams of pure alcohol, alcohol calories). It explicitly distinguishes the unit from UK (8 g) and US (14 g) measures, so an agent cannot confuse it with a generic drinks 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 concrete example phrasings that should route here ('how many standard drinks in a bottle of wine', 'standard drinks in a can of rtd'), states national scope, and gives explicit when-NOT-to-use guidance: it does not estimate blood/breath alcohol and must not be used to answer whether someone can drive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Calculate.co.nz NZ Calculators toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources