Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_take_home

Take-home pay (Australia) [AU]. Annual income tax, low income tax offset, 2% Medicare levy, optional HELP repayment and take-home pay for an Australian resident in 2026-27, plus employer super at 12%.

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": {
      "annualGross": "<annualGross>"
    },
    "name": "au_take_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
annualGrossYesGross annual salary in AUD, excluding super
hasHelpDebtNoWhether the person has a HELP/HECS debt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 burden: it does disclose the tax year (2026-27), the residency assumption, and the exact set of figures computed, which is real behavioral context. However, it never states that this is a side-effect-free projection rather than a filing/payment, does not note that results are estimates subject to rounding or rule changes, and says nothing about the shape of the response despite there being no output schema.

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?

A single dense sentence that front-loads the resource and then lists components; every clause carries information. It is slightly run-on, packing output fields and assumptions into one breath, but there is no filler.

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 two-parameter calculator with no output schema, enumerating the computed outputs (take-home, tax, LITO, levy, HELP, super) is genuinely useful and largely covers what the agent needs. It still omits whether the return is a single figure or a breakdown, and gives no guidance on choosing this tool over its component siblings.

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 100%, so both parameters are already documented, and the description only reinforces them by noting that the gross figure excludes super and that HELP repayment is optional (mapping to hasHelpDebt). It adds no format, range, or unit nuance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific computation and jurisdiction ('Take-home pay (Australia) [AU]') and enumerates exactly which components it computes (income tax, LITO, 2% Medicare levy, HELP, employer super at 12%), which is enough to separate it from nz_take_home. It does not explicitly distinguish itself from the more granular siblings au_help_repayment, au_mls, or au_super, so the differentiation is only partial.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling tools that compute the same individual components (au_help_repayment, au_mls, au_super). An agent must infer that this is the all-in-one estimate rather than the component calculators, entirely from the name and the list of included levies.

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