Skip to main content
Glama

CheckMyTax NZ: New Zealand Tax Calculators

nz_gst

GST (New Zealand) [NZ]. Adds 15% NZ GST to a GST-exclusive amount, or works out the GST inside a GST-inclusive amount (3/23 of it).

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": {
      "amount": "<amount>",
      "mode": "<mode>"
    },
    "name": "nz_gst"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesadd = amount excludes GST; remove = amount includes GST
yearNoNZ tax year, e.g. "2026-27". Supported: 2026-27.
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the 15% rate and the 3/23 inclusive extraction formula, which is valuable behavioral detail, but it does not specify the return value, rounding behavior, currency handling, or how the optional year affects the calculation.

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 two compact sentences with no wasted wording, and the core calculation behavior is front-loaded. It is appropriately sized for a simple calculator tool.

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

Completeness3/5

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

For a simple calculation tool, the description explains both modes and the GST fractions well enough to invoke it. But without annotations or an output schema, it should ideally clarify what is returned for add mode versus remove mode, along with rounding and year behavior.

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

Parameters3/5

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

Schema description coverage is 67%, so the schema already documents mode and year, and the description reinforces the amount interpretation for each mode. However, it adds no explanation for the optional year parameter or how unsupported years are handled.

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 domain and operation: New Zealand GST, adding 15% to GST-exclusive amounts or extracting the GST component from inclusive amounts. The [NZ] marker also helps distinguish it from the au_gst sibling.

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 clearly explains that one mode is for GST-exclusive amounts and the other for GST-inclusive amounts, which effectively tells the agent when to use each mode. It does not explicitly discuss alternatives or exclusions, but the NZ scope and mode mapping are 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