Skip to main content
Glama

BRAINIAC Indirect Tax Calculations

Australia and New Zealand GST registration threshold

indirect-tax_australia-nz-gst
Read-onlyIdempotent

Test AU/NZ GST registration thresholds from monthly turnover and optionally extract GST from an inclusive or exclusive price. Use when you need australia and new zealand gst registration threshold as a paid JSON result with no API key.

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": {
      "country": "<country>",
      "monthlyTurnoverCents": "<monthlyTurnoverCents>",
      "projectedNextMonthsCents": "<projectedNextMonthsCents>"
    },
    "name": "indirect-tax_australia-nz-gst"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYescountry, string, one of AU, NZ. Required.
nonProfitNononProfit, boolean. Required.
priceCentsNopriceCents, integer, from 0 to 9007199254740991. Optional.
priceIncludesGstNopriceIncludesGst, boolean. Required.
taxiOrRideSourcingNotaxiOrRideSourcing, boolean. Required.
monthlyTurnoverCentsYesmonthlyTurnoverCents, array. Required.
projectedNextMonthsCentsYesprojectedNextMonthsCents, array. Required.

Output Schema

NameRequiredDescriptionDefault
rateNorate. Number.
reasonNoreason. String.
sourcesNosources. Array.
gstCentsNogstCents. Number.
netCentsNonetCents. Number.
thresholdNothreshold. Number.
limitationsNolimitations. Array.
mustRegisterNomustRegister. Boolean.
currentTurnoverNocurrentTurnover. Number.
projectedTurnoverNoprojectedTurnover. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results are a paid JSON response with no API key required, which is useful context not in the annotations, but says nothing about cost, rate limits, or how the threshold is evaluated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, with the primary purpose front-loaded. The second sentence is largely a restatement plus marketing-style wording ('as a paid JSON result with no API key'), which is informative but awkwardly phrased and partly redundant with the first.

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?

An output schema exists, so return values need not be explained, and all seven parameters are documented in the schema. However, for a threshold calculator with materially different conditions (nonProfit, taxiOrRideSourcing, projected future turnover), the description does not explain how these affect the result, leaving a moderate gap.

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 baseline is 3. The description clarifies that monthlyTurnoverCents drives threshold testing and that priceCents plus priceIncludesGst control the optional GST extraction, but it adds no meaning for nonProfit, taxiOrRideSourcing, or projectedNextMonthsCents beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: test AU/NZ GST registration thresholds from monthly turnover, with an optional GST extraction from inclusive/exclusive price. The jurisdictional scope gives some separation from siblings, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The only guidance is 'Use when you need australia and new zealand gst registration threshold', which restates the purpose rather than adding conditions. There is no when-not guidance, no mention of alternatives such as the EU OSS threshold check, and no explanation of when the nonProfit or taxiOrRideSourcing paths matter.

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