Skip to main content
Glama
Sign In

au-compliance-kit

by io.github.aftertaxau
OverviewDiscussionsAdmin

Salary needed for a target take-home pay

salary_for_take_home
Read-onlyIdempotent

Works backwards from the take-home pay someone wants to the gross annual salary they need in Australia, for 2025-26 or 2026-27. Give the target take-home per week, fortnight, month or year; returns the salary needed (excluding super), the take-home and tax withheld for each pay period, and the employer's super on top. Use it for salary negotiations and questions like 'what do I need to earn to take home $1,500 a week'. It uses the same ATO withholding formulas as take_home_pay. AUD. Read-only and deterministic.

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": {
      "takeHome": "<takeHome>",
      "per": "<per>"
    },
    "name": "salary_for_take_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
perYesThe period takeHome is for.
taxYearNoAustralian financial year (1 July to 30 June) whose withholding tables to use. Default 2026-27.
takeHomeYesTake-home pay wanted, in AUD, for the period in 'per', e.g. 1500.
studyLoanNoHas a HELP, VSL, SSL or other study and training support loan. Default false.
foreignResidentNoForeign resident for tax purposes. Default false.
taxFreeThresholdNoTax-free threshold claimed with this employer. Default true (main job). Use false for a second job.

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?

Annotations already declare readOnly, idempotent and non-destructive, so 'read-only and deterministic' is largely repetition. The description does add genuine behavioral context beyond them: the returned salary excludes super while employer super is reported on top, the breakdown is per pay period, and the calculation reuses the same ATO formulas as a named sibling — all useful for trusting the number.

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?

Core behavior, input shape and output shape are front-loaded in the first two sentences, then usage and a worked example. The closing 'AUD. Read-only and deterministic.' is short and largely restates structured data, a minor redundancy rather than bloat.

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, and the description compensates by enumerating the return payload (required salary, take-home and tax withheld per period, employer super). Combined with jurisdiction, tax-year scope and the super exclusion, an agent has what it needs; only edge cases like an unattainable or zero target are unaddressed.

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 every parameter (per, taxYear, takeHome, studyLoan, foreignResident, taxFreeThreshold) has its own description with enums and defaults. The description reinforces the period choice and the target-take-home semantics but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — works backwards from a target take-home to the required gross annual salary — and pins the jurisdiction and tax years. It is unmistakably the inverse of take_home_pay, so an agent can separate the two from the description alone.

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?

Gives a concrete usage scenario and a natural-language example question ('what do I need to earn to take home $1,500 a week') plus the negotiation context. The inverse relationship to take_home_pay is implied via 'same ATO withholding formulas', but it never explicitly states 'if you already know the salary, use take_home_pay instead'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All au-compliance-kit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources