Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_novated_lease

Novated lease savings (Australia) [AU]. Estimates the yearly saving from a novated lease for 2026-27: GST credits, the pre-tax deduction, tax saved and the employee contribution method (20% statutory formula), including the electric car FBT exemption. Doesn't apply the proposed EV changes from 1 April 2027, the operating cost method, balloon payments, fees or super effects.

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": {
      "salary": "<salary>",
      "annualCosts": "<annualCosts>",
      "baseValue": "<baseValue>",
      "vehicle": "<vehicle>"
    },
    "name": "au_novated_lease"
  }
}

Input Schema

NameRequiredDescriptionDefault
salaryYesGross annual salary before the lease
vehicleYeselectric = battery electric or hydrogen; plug-in hybrids no longer qualify for the exemption
baseValueYesCar base value: GST-inclusive cost price plus delivery and accessories, excluding registration and stamp duty
annualCostsYesTotal yearly lease and running costs (finance, fuel or charging, insurance, rego, servicing, tyres), GST-inclusive
hasHelpDebtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the calculation mechanics (GST credits, pre-tax deduction, ECM 20% statutory formula, EV FBT exemption) and explicitly bounds the model by listing what it does not apply. It stops short of stating that this is a pure computation with no side effects, but the limitation list is substantive and honest.

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?

Two sentences, front-loaded with purpose before scope and exclusions. The exclusion list is dense but every clause restricts the model in a way an agent could otherwise get wrong; minor cost is that the first sentence runs long.

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

Completeness4/5

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

There is no output schema, so the description must convey what comes back; it lists the estimated components (GST credits, pre-tax deduction, tax saved, employee contribution) which is close to sufficient. A reader still doesn't know the response structure or whether a total saving figure is returned alongside the breakdown.

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 coverage is already 80%, so the schema handles most parameter meaning. The description still adds interpretive value by tying the 20% statutory formula and the EV FBT exemption to the calculation, which explains why baseValue and vehicle matter. The undocumented hasHelpDebt parameter is left uncovered in both places.

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 ("Estimates the yearly saving from a novated lease"), names the jurisdiction and tax year (Australia, 2026-27), and enumerates the components computed. An agent can tell this apart from the sibling take-home or GST calculators without any further reading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the exclusions: an agent learns not to reach for it for post-1-April-2027 EV rules, the operating cost method, balloon payments, fees or super effects. However, it never names an alternative tool or states positively when this one should be selected over au_take_home or au_super.

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