Skip to main content
Glama

TaxCheck AU: Australian Tax Calculators

au_gst

GST (Australia) [AU]. Adds 10% Australian GST to a GST-exclusive amount, or works out the GST inside a GST-inclusive amount (1/11 of it).

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": {
      "amount": "<amount>",
      "mode": "<mode>"
    },
    "name": "au_gst"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesadd: amount is GST-exclusive; remove: amount is GST-inclusive
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 burden and does disclose the core behavior: it is a deterministic calculation with the exact rates (10% addition, 1/11 extraction). It omits rounding/cent-precision rules and the shape of the result, which matter for a money calculator but are secondary to the arithmetic itself.

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?

One front-loaded sentence that gives the operation, the rate, and both formulas with zero filler. Nothing could be removed without losing information.

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 simple two-parameter calculator with no output schema, the description should still say what is returned for each mode (GST component versus total) and how rounding is handled. Those gaps are meaningful because there is no output schema to fall back on.

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 50%: the mode enum already documents 'add = GST-exclusive, remove = GST-inclusive', and the description largely restates that mapping. It adds the meaning of the computed output for each mode but says nothing extra about amount beyond the schema's minimum-of-zero constraint, so it does not fully compensate for the coverage gap.

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 operation on a specific resource: adding 10% Australian GST to a GST-exclusive amount or extracting the 1/11 GST component of an inclusive amount. The '(Australia) [AU]' qualifier separates it from the nz_gst sibling without needing to open either schema.

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

Usage Guidelines3/5

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

The two modes are described so an agent can infer which branch to pick from the amount's tax basis, but there is no explicit 'use this when' framing, no statement of prerequisites, and no naming of alternatives such as nz_gst for other jurisdictions. Usage is implied rather than directed.

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