Skip to main content
Glama
UseCOS MCP Server

UseCOS MCP Server

by rivlosys

calculate_canadian_gst_hst

Calculates Canadian GST, PST, and HST by province, or reverse-extracts the tax portion from a tax-included total for receipts.

Instructions

Calculate or reverse-extract Canadian GST, PST, and HST for any province or territory.

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": "calculate_canadian_gst_hst"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesPre-tax subtotal (if includeInTotal=false) or tax-included receipt total (if includeInTotal=true)
provinceNoON
includeInTotalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say which tax types apply per province (e.g., that AB has no PST, or that QC uses QST), whether rates are current or configurable, how rounding is handled, or what the response contains. For a calculation tool with zero annotation coverage these are meaningful gaps.

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?

A single front-loaded sentence with no filler; the verb and scope appear before any qualifiers. Nothing in it is redundant.

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

Completeness2/5

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

For a three-parameter tool with no annotations, no output schema, and low schema description coverage, the description is too thin. An agent still cannot tell what the return value looks like (single total vs. per-tax breakdown) or which provincial tax rules are applied, both of which matter for calling and interpreting this tool correctly.

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 only 33%, with 'province' and 'includeInTotal' undocumented in the schema. The description partially compensates: 'reverse-extract' maps onto includeInTotal, and 'any province or territory' signals the province parameter's role. It still adds no detail on the default of ON, the enum list, or how province selection changes which taxes are computed.

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?

The description names a specific verb pair (calculate / reverse-extract) and a specific resource (Canadian GST, PST, and HST), scoped to 'any province or territory'. This is clearly distinguishable from siblings like calculate_canadian_mortgage or calculate_canadian_paycheck without opening the schema. It stops short of 5 only because it doesn't explicitly contrast itself with those siblings.

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 phrase 'Calculate or reverse-extract' signals that the tool supports two directions of operation, which is implied guidance about when each mode applies. However, it never states when to use this tool versus the other Canadian calculators, nor does it tie the reverse mode to the includeInTotal flag explicitly. Usage must largely be inferred from the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.