Aus Accounting MCP

Calculate a bounded Australian tax worksheet

calculate_tax_worksheet

Read-onlyIdempotent

Compute tax worksheet amounts for GST, resident basic tax, capital gains, FBT, depreciation, or quarterly SG. Supply established facts and confirmed scope to get cited results.

Instructions

Calculate GST, resident basic tax, CGT, FBT, depreciation or quarterly SG.

Each kind has a bounded scope and period in aus-accounting://scope. Most cover 2025-26; resident basic tax also covers 2024-25 and 2026-27. FBT covers the year ended 31 March 2026. Require operator-established classifications and eligibility. Pass scope_confirmed true only after establishing every scope condition listed in calculation_worksheets for the kind; resolve missing or uncertain scope first. Scope confirmation is not evidence of eligibility. Never invent it. Every money field is a non-negative AUD decimal string, at most 2 decimal places and at most 1000000000000.00. Results include engine version, source-check date, citations and exclusions. These worksheets do not prepare a BAS or return, calculate Medicare/HELP, value benefits or assets, or establish post-June 2026 SG entitlement. All maths stays in australian-tax-calculators. Local review aid, not advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`facts`	Yes	Established facts for one worksheet kind. Read calculation_worksheets in aus-accounting://scope before confirming scope. Supply established zero amounts explicitly; do not infer missing facts.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	The review ran; this does not mean compliance or a known verdict.
`rates`	Yes
`scope`	Yes
`engine`	Yes	Delegated distribution that produced this result.
`period`	Yes
`amounts`	Yes
`sources`	Yes
`warnings`	Yes
`calculation`	Yes
`engine_version`	Yes	Installed version of that engine.
`source_checked`	Yes	Date in YYYY-MM-DD form.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.1.13Sep 21, 2026

changedInput schema / $defs / CapitalGainsFacts / properties / current_losses / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / CapitalGainsFacts / properties / discount_gains / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / CapitalGainsFacts / properties / other_gains / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / CapitalGainsFacts / properties / prior_losses / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / CapitalGainsFacts / properties / scope_confirmed / description

Previous value: -"Pass true only after establishing every scope condition in aus-accounting://scope calculation_worksheets for this kind. Missing or uncertain scope must be resolved first; false is refused."New value: +"Scope confirmation for this kind; false is refused."

changedInput schema / $defs / DepreciationFacts / properties / cost / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / DepreciationFacts / properties / scope_confirmed / description

Previous value: -"Pass true only after establishing every scope condition in aus-accounting://scope calculation_worksheets for this kind. Missing or uncertain scope must be resolved first; false is refused."New value: +"Scope confirmation for this kind; false is refused."

changedInput schema / $defs / FbtFacts / properties / scope_confirmed / description

Previous value: -"Pass true only after establishing every scope condition in aus-accounting://scope calculation_worksheets for this kind. Missing or uncertain scope must be resolved first; false is refused."New value: +"Scope confirmation for this kind; false is refused."

changedInput schema / $defs / FbtFacts / properties / type_one_value / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / FbtFacts / properties / type_two_value / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / GstFacts / properties / amount / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / GstFacts / properties / scope_confirmed / description

Previous value: -"Pass true only after establishing every scope condition in aus-accounting://scope calculation_worksheets for this kind. Missing or uncertain scope must be resolved first; false is refused."New value: +"Scope confirmation for this kind; false is refused."

changedInput schema / $defs / ResidentTaxFacts / properties / scope_confirmed / description

Previous value: -"Pass true only after establishing every scope condition in aus-accounting://scope calculation_worksheets for this kind. Missing or uncertain scope must be resolved first; false is refused."New value: +"Scope confirmation for this kind; false is refused."

changedInput schema / $defs / ResidentTaxFacts / properties / taxable_income / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / SgFacts / properties / ordinary_time_earnings / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / SgFacts / properties / qualifying_contributions / description

Previous value: -"Non-negative AUD decimal string, at most 2dp and 1000000000000.00."New value: +"AUD decimal string."

changedInput schema / $defs / SgFacts / properties / scope_confirmed / description

Previous value: -"Pass true only after establishing every scope condition in aus-accounting://scope calculation_worksheets for this kind. Missing or uncertain scope must be resolved first; false is refused."New value: +"Scope confirmation for this kind; false is refused."

Addedv0.1.10Sep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that results include engine version, source-check date, citations and exclusions, and that it never invents scope_confirmed. It also clarifies it's a local review aid, not advice, and that all maths stays in australian-tax-calculators. This goes beyond the annotations, though it could have mentioned more about the output structure.

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 description is long but information-dense. It front-loads the purpose, then covers scope, requirements, constraints, output, exclusions, and limitations in a logical order. Every sentence contributes essential information for correct usage; there is no filler.

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?

Given the tool's complexity (six worksheet kinds with distinct facts), the description is remarkably complete. It specifies scope periods, the requirement to confirm scope, money format, output contents, and what it does not do. With a detailed input schema and an output schema present, an agent has enough to call this correctly. Minor gaps: it doesn't give examples of each kind, but that's covered by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with field descriptions, but the description adds global constraints: every money field is a non-negative AUD decimal string with max 2 decimals and max 1000000000000.00. It also adds semantics for the facts parameter ('Supply established zero amounts explicitly; do not infer missing facts') and for scope_confirmed ('false is refused' and the rule to only pass true after establishing scope). This adds meaning 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 starts with 'Calculate GST, resident basic tax, CGT, FBT, depreciation or quarterly SG', specifying the verb 'Calculate' and listing six distinct tax kinds. This clearly distinguishes it from sibling tools like get_ato_benchmarks or search_tax_legislation, which serve different purposes.

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?

It gives explicit conditions: each kind has a bounded scope in aus-accounting://scope, and scope_confirmed must only be passed true after verifying all conditions in calculation_worksheets. It also lists exclusions (does not prepare a BAS/return, calculate Medicare/HELP, etc.) and notes it's a local review aid, not advice. However, it doesn't explicitly name sibling tools as alternatives for those exclusions.

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

Deploy Server