Skip to main content
Glama
Sign In

au-compliance-kit

by io.github.aftertaxau
OverviewDiscussionsAdmin

GST calculation

gst_calculation
Read-onlyIdempotent

Adds 10% Australian GST to a price, or works out the GST included in a GST-inclusive price (the price divided by 11). Returns the price excluding GST, the GST and the price including GST, rounded to the cent. Use it for invoices, quotes and receipts. It doesn't decide whether an item is GST-free or input-taxed. 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": {
      "amount": "<amount>"
    },
    "name": "gst_calculation"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesThe price in AUD, e.g. 110.
includesGstNotrue if amount already includes GST (to take it out). Default false (GST is added).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), yet the description adds real behavioral content: the exact formula, rounding to the cent, determinism, and the three values returned (exclusive, GST, inclusive). This compensates meaningfully for the absent output schema.

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?

Front-loads the two operating modes, then the return values, then the usage note and the exclusion. The only waste is 'Read-only', which restates readOnlyHint; 'deterministic' and 'AUD' earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter pure calculator with no output schema, the description supplies everything an agent needs: both directions of calculation, currency, rounding, the full return tuple, and the limit of its judgement. Nothing operational is left to guess.

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%, so the baseline is 3, but the description adds interpretive value by spelling out the arithmetic behind 'includesGst' ('the price divided by 11') and by pinning the currency to AUD. The amount's non-negative constraint and example remain schema-only, so it is not exhaustive.

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 ('Adds 10% Australian GST to a price') and then names the inverse mode ('works out the GST included in a GST-inclusive price'). The parenthetical formula ('the price divided by 11') makes the operation unambiguous and clearly distinct from the payroll/withholding siblings.

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 concrete usage contexts ('Use it for invoices, quotes and receipts') and an explicit scope boundary ('It doesn't decide whether an item is GST-free or input-taxed'), which tells the agent when this tool is insufficient. It stops short of naming an alternative tool for the taxability question, so routing is only partially resolved.

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