Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_mls

Medicare levy surcharge (Australia) [AU]. Works out whether an Australian resident pays the Medicare levy surcharge (MLS) for an income year, which tier applies, how much they'd pay, and the yearly hospital-cover premium below which cover is cheaper than the surcharge. Use it for 'do I need private health insurance to avoid the MLS?' questions. Doesn't handle the low-income spouse exemption, part-year couples or dependants, or super lump sums.

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": {
      "you": "<you>"
    },
    "name": "au_mls"
  }
}

Input Schema

NameRequiredDescriptionDefault
youYes
yearNoIncome year, e.g. "2026-27". Supported: 2025-26, 2026-27.
spouseNoLeave out if single
daysWithoutCoverNoDays this year without appropriate private hospital cover (default: whole year)
dependentChildrenNoMLS dependent children

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and it does disclose the shape of the result (tier, surcharge amount, breakeven premium) and the boundary conditions where results are unreliable. It adds no auth/purity statement, though for a pure statutory calculator that omission is minor.

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?

Three sentences, front-loaded with the resource and the computed outputs, followed by the likely user question and then the caveats. Nothing is redundant; the exclusions are stated compactly as a single clause.

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?

With 5 parameters, nested objects and no output schema, the description supplies enough for correct invocation by explaining what is returned and where results break down. One tension remains: it says it doesn't handle 'dependants' while the schema accepts a dependentChildren field, leaving the agent unsure whether that input is honoured or ignored.

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 80% and the nested 'you'/'spouse' objects document each income component, the default for daysWithoutCover and the supported years, so the schema does the heavy lifting. The description adds essentially no extra parameter meaning beyond naming the income year and resident status, which is the baseline-3 case.

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?

Specific verb+resource: states it works out whether an Australian resident pays the Medicare levy surcharge, which tier applies, the amount payable, and the annual hospital-cover premium threshold at which cover beats the surcharge. It also scopes the domain ('income year', 'Australian resident'), which cleanly separates it from the NZ and non-MLS siblings in the catalog.

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

Usage Guidelines5/5

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

Gives an explicit use case in the user's own words ('do I need private health insurance to avoid the MLS?') plus explicit exclusions: low-income spouse exemption, part-year couples, dependants, super lump sums. Telling the agent when the answer would be wrong is the highest-value form of guidance for a calculator like this.

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