Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_public_holidays

Public holidays and business days (Australia) [AU]. Lists Australian public holidays by state or territory for 2026 and 2027, checks whether a date is a business day, adds or subtracts business days, and counts business days between two dates (Monday to Friday, excluding public holidays). Regional and show-day holidays are excluded unless includeRegional is true, and partial-day holidays (Christmas Eve, New Year's Eve) are not treated as full days. Only 2026 and 2027 are supported; other years return an error.

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": {
      "mode": "<mode>",
      "region": "<region>"
    },
    "name": "au_public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNobusiness_days_between: end date (counted)
dateNois_business_day, add_business_days: the date
daysNoadd_business_days: whole business days to add (negative to go back)
modeYeslist: public holidays in a year; is_business_day: is a date a working day; add_business_days: move a date forward or back by business days; business_days_between: count business days after start up to and including end
yearNolist: calendar year
startNobusiness_days_between: start date (not counted)
regionYesState or territory (required)
extraHolidaysNoExtra non-working dates, e.g. a shutdown
includeRegionalNoAU: count regional holidays such as show days; default false
includeMondayisedNoNZ: count Mondayised holidays; default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the business-day rule (Mon-Fri excluding public holidays), the exclusion of regional and show-day holidays by default, the special handling of partial-day holidays like Christmas Eve and New Year's Eve, and the hard 2026/2027 year limit that produces an error. It stops short of describing error behavior for invalid regions or dates, and says nothing about response format.

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 content is front-loaded with the tool's identity and scope, and every sentence carries information. It is a single dense paragraph that would read better split into purpose/constraints lines, 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 four-mode tool with ten parameters and no output schema, the description covers inputs and constraints thoroughly but never indicates what each mode returns (a holiday list, a boolean, a shifted date, a count). An agent can call it, but cannot predict result shape without experimentation.

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 the schema already documents all ten parameters including mode enum semantics. The description reinforces meaning for includeRegional (regional holidays such as show days) and defines what a business day is, but adds no guidance on the AU-irrelevant includeMondayised flag or interactions between extraHolidays and counting. Baseline 3 is appropriate.

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 names specific verbs and resources: listing AU public holidays by state/territory for 2026-2027, checking business days, adding/subtracting business days, and counting business days between dates. The '[AU]' tag plus the state/territory scope distinguishes it from the nz_public_holidays sibling without ambiguity.

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 establishes clear operating conditions: only 2026 and 2027 are supported (other years error out), regional/show-day holidays only when includeRegional is true, and partial-day holidays are not full days. It does not explicitly route an agent to nz_public_holidays for New Zealand, but the '[AU]' prefix and state enum make the scope clear.

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