Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_super

Super contributions (Australia) [AU]. Works out employer super guarantee (12%), total concessional contributions against the 2026-27 cap of $32,500, how much room is left or how much is excess, 15% contributions tax and net into the fund. Flags when Division 293 may apply. Doesn't cover carry-forward amounts, non-concessional contributions or Division 293 tax amounts.

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>"
    },
    "name": "au_super"
  }
}

Input Schema

NameRequiredDescriptionDefault
salaryYesAnnual salary (ordinary time earnings) in AUD, before salary sacrifice
salarySacrificeNoSalary sacrificed into super per year
personalDeductibleNoPersonal contributions you will claim a deduction for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 disclosure burden. It does well on outputs — listing the computed figures and the Division 293 flag — but says nothing about the operation being a side-effect-free calculation, assumptions such as ordinary time earnings, rounding, or that the 2026-27 cap and 12% rate are fixed rather than parameterised.

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?

Two dense sentences, front-loaded with what is computed, then the exclusions. Every clause carries content — no filler, no restatement of the name or title.

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?

For a pure three-parameter calculator with a fully described schema and no output schema, this covers outputs and scope exclusions adequately. It lacks only the qualifiers an agent might want before trusting results — fixed tax year/rates, currency, and whether the calculation is stateless.

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 each parameter already documents itself, so the baseline is 3. The description implies salary sacrifice and personal deductible contributions roll into the concessional total, which adds a little domain meaning, but it never explicitly maps the three inputs to the computations.

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?

Names the specific resource (Australian super contributions) and verb (works out), then enumerates exactly what is computed: 12% SG, concessional total vs the $32,500 cap, remaining room or excess, 15% contributions tax and net into fund. The explicit carve-outs (no carry-forward, non-concessional or Div 293 amounts) further separate it from adjacent calculators like au_take_home.

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?

Scope boundaries are stated clearly, including a 'doesn't cover' list that tells the agent when this tool will not answer the question. It does not name an alternative tool to use for the excluded cases (carry-forward, non-concessional, Div 293 amounts), so routing in those situations is left to inference.

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