Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_help_repayment

HELP / HECS compulsory repayment (Australia) [AU]. Compulsory HELP repayment for 2026-27 under the marginal system: nil to $69,528, 15c above, then 17c, then 10% of repayment income above $186,050.

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": {
      "repaymentIncome": "<repaymentIncome>"
    },
    "name": "au_help_repayment"
  }
}

Input Schema

NameRequiredDescriptionDefault
repaymentIncomeYesHELP repayment income in AUD: taxable income plus reportable fringe benefits, net investment losses and reportable super

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are present, so the description must carry the behavioral disclosure. It reveals that this is a rate-schedule calculation for a specific year and gives several thresholds and rates, but it omits the starting threshold for the 17c band and does not state output units, rounding, or returned amount.

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 definition is short and front-loaded with jurisdiction, obligation, year, and rate schedule. The repeated 'HELP / HECS compulsory repayment' and 'Compulsory HELP repayment' phrasing is slightly redundant but not wasteful.

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 one-parameter calculator, the description supplies the core rate schedule and scope. However, with no annotations and no output schema, it should more fully specify the missing 17c threshold, rate units, rounding, and returned amount.

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 coverage is 100% and the sole repaymentIncome parameter is fully defined in the schema, including its AUD composition. The description reinforces that the calculation operates on repayment income and supplies rate thresholds, but adds no syntax or alternative input details beyond the 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 names the specific obligation (HELP/HECS compulsory repayment), jurisdiction [AU], and tax year 2026-27, and outlines the marginal rate structure. This clearly distinguishes it from generic take-home, GST, and other sibling calculators.

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?

It implies use for calculating Australian HELP compulsory repayments in 2026-27 by providing the applicable marginal schedule, but it does not explicitly say when to choose it over siblings such as au_take_home or when not to use it. The usage context is inferable but not explicitly stated.

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