Skip to main content
Glama

HomeCalc — Canadian Mortgage & Tax Calculators

Canadian Land Transfer Tax Calculator

land_transfer_tax
Read-only

Estimate land transfer tax on a home purchase in any of the 13 provinces and territories (incl. Toronto MLTT, Montreal welcome tax) with first-time buyer rebates, the transfer registration fee (to register the deed) and the total due at registration. AB, SK, NL and the territories charge no land transfer tax, only the registration fee. The mortgage registration fee is not included.

Input Schema

NameRequiredDescriptionDefault
priceYesPurchase price in CAD
provinceYesProvince or territory
inTorontoNoOntario only: property is within the City of Toronto (adds the municipal LTT)
isFirstTimeBuyerNoFirst-time buyer (rebate where one exists)
quebecMunicipalityNoQuebec only: 'montreal' = Montreal's welcome-tax brackets (default); 'other' = provincial base schedule, for municipalities without higher rates above $500,000montreal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "inToronto": true,
      +    "isFirstTimeBuyer": true,
      +    "price": 750000,
      +    "province": "Ontario"
      +  }
      +]
    • addedInput schema / properties / isFirstTimeBuyer / description
      Added value: +"First-time buyer (rebate where one exists)"
    • changedInput schema / properties / quebecMunicipality / description
      Previous value: -"Quebec only: 'montreal' uses Montreal's welcome-tax brackets (the website's Quebec default); 'other' uses the provincial base schedule for municipalities without higher rates above $500,000"New value: +"Quebec only: 'montreal' = Montreal's welcome-tax brackets (default); 'other' = provincial base schedule, for municipalities without higher rates above $500,000"
  2. 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, non-destructive, closed-world behavior. The description adds useful behavioral context: geographic coverage, municipal add-ons (Toronto MLTT, Montreal welcome tax), first-time buyer rebates, what fees are included vs. excluded, and zero-LTT jurisdictions. It doesn't specify tax-year/rate version, but that is a modest gap.

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?

Three dense, front-loaded sentences with no wasted words. Purpose comes first, followed by scope/special cases and an important exclusion.

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?

No output schema exists, but the description signals the return components (tax, rebate, registration fee, total due at registration), which is sufficient for an agent to know what to expect. Slightly more detail on output structure could help, but it is largely complete for a read-only calculator.

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 schema already documents every parameter including inToronto, isFirstTimeBuyer, and quebecMunicipality. The description reinforces province-specific behavior but adds no syntax, format, or mapping details beyond what the schema provides.

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 ('Estimate') and resource ('land transfer tax on a home purchase') with scope across 13 provinces/territories. It explicitly names special cases (Toronto MLTT, Montreal welcome tax) and distinguishes itself from all siblings, which cover different taxes or mortgage calculations.

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?

Clear context: use for home-purchase land transfer tax estimation. Notes exclusions ('mortgage registration fee is not included') and special cases where no LTT applies (AB, SK, NL, territories). No explicit sibling alternative exists, so the lack of a 'use X instead' line 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