Skip to main content
Glama

BRAINIAC Indirect Tax Calculations

Canada GST/HST and PST rate and tax amount

indirect-tax_canada-gst-hst-pst
Read-onlyIdempotent

Look up GST/HST (and PST where the CRA table lists one) for a province and date, and compute tax on an amount in cents before you charge or file indirect tax. Call with province, date, and amountCents; optional supply. Returns regime, gstOrHstRate, pstRate, gstOrHstCents, pstCents, totalCents, and effectiveFrom. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: before you charge or file indirect tax, province, date, amountCents, supply, regime, gstOrHstRate, pstRate, gstOrHstCents, pstCents, totalCents, effectiveFrom, Canada GST/HST and PST rate and tax amount, canada gst hst pst.

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": {
      "province": "<province>",
      "date": "<date>",
      "amountCents": "<amountCents>"
    },
    "name": "indirect-tax_canada-gst-hst-pst"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesdate, string, date. Required.
supplyNosupply, string, one of taxable, zero_rated. Required.taxable
provinceYesprovince, string, one of AB, BC, MB, NB, NL, NT. Required.
amountCentsYesamountCents, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
regimeNoregime. String.
pstRateNopstRate. Null.
sourcesNosources. Array.
pstCentsNopstCents. Number.
totalCentsNototalCents. Number.
limitationsNolimitations. Array.
gstOrHstRateNogstOrHstRate. Number.
effectiveFromNoeffectiveFrom. String.
gstOrHstCentsNogstOrHstCents. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond them: billing semantics ('HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged') and the presence of an effectiveFrom versioning field. It stops short of stating rounding rules or auth requirements.

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?

The core sentences are dense and front-loaded with the action and the returned fields. However, the trailing 'Keywords:' block restates the parameters, return fields, title, and case variants of the name, which is filler that duplicates structured data rather than adding meaning.

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?

With an output schema present, the field list is redundant but harmless, and billing semantics are covered. For a rate computation tool the remaining gap is rounding/precision behavior on totalCents and what 'partial' status means, which would matter when computing tax on an amount.

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. The description earns an extra point by resolving a real ambiguity: the schema's own supply description says 'Required.' while the required array omits it, and the description clarifies it is 'optional'. It also reinforces that the amount is in cents.

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 pair ('look up GST/HST... for a province and date') plus the second function ('compute tax on an amount in cents'), and scopes it to Canada with a PST caveat about the CRA table. An agent can separate this from the Australia/NZ, UK VAT, and EU OSS siblings purely from the text.

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 a clear trigger condition: 'before you charge or file indirect tax'. It does not name explicit exclusions or point to an alternative tool, but the jurisdiction scoping makes overlap with siblings unlikely, so the missing piece is minor.

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