Skip to main content
Glama
UseCOS MCP Server

UseCOS MCP Server

by rivlosys

calculate_canadian_mortgage

Calculate Canadian mortgage payments with semi-annual compounding, CMHC insurance, provincial land transfer tax, and OSFI B-20 stress-test results from price, rate, and down payment.

Instructions

Calculate Canadian mortgage payment (semi-annual compounding), CMHC insurance, provincial land transfer tax, and OSFI B-20 stress-test payment.

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": {
      "price": "<price>",
      "rate": "<rate>"
    },
    "name": "calculate_canadian_mortgage"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNopurchase
rateYesNominal annual interest rate in percent (e.g. 4.79)
amortNoAmortization period in years
priceYesHome purchase price or mortgage balance in CAD
provinceNoON
frequencyNomonthly
downPaymentNoDown payment in CAD
lumpSumYearNo
extraPaymentNo
lumpSumAmountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add genuine domain context beyond the name: semi-annual compounding (the Canadian convention), plus the fact that CMHC insurance, provincial land transfer tax, and the OSFI B-20 stress test are all computed, which tells the agent this is a multi-output regulatory calculator rather than a plain payment formula. However, it never states that the tool is a pure side-effect-free computation, what the response shape is, or which assumptions (e.g. insurance premium tiers, stress-test qualifying rate) are baked in.

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?

A single dense sentence with zero filler, and the core purpose is front-loaded before the list of computed outputs. It is efficient, though the telegraphic style (no explicit subject) makes it read more like a label than an instruction, and it uses its brevity at the cost of the guidance noted above.

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?

For a 10-parameter financial calculator with no annotations and no output schema, the description should explain both the return values and the key input assumptions. Naming the four computed components partially substitutes for the missing output schema, but it does not say what the response structure looks like or how provincial tax, CMHC premiums, and stress-test figures are presented, and it leaves the undocumented parameters unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40% across 10 parameters, so the description must compensate and largely does not. Terms like 'semi-annual compounding', 'CMHC insurance', and 'land transfer tax' hint at the relevance of rate, downPayment, and province, but the description never maps inputs to those outputs. Six parameters — mode, province, frequency, lumpSumYear, extraPayment, lumpSumAmount — receive no explanation of their effect on the result, leaving an agent to guess how prepayments or payment frequency alter the calculation.

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 (Calculate) and a well-scoped resource (Canadian mortgage), then enumerates the four outputs it produces: payment, CMHC insurance, land transfer tax, and B-20 stress-test payment. That enumeration makes it clearly distinct from the sibling calculators (auto loan, GST/HST, paycheck, renewal comparison). It stops short of 5 only because the parenthetical '(semi-annual compounding)' is the sole disambiguation cue, and no explicit contrast with a sibling is stated.

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?

There is no when-to-use or when-not-to-use guidance. Nothing tells an agent when to pick 'purchase' vs 'refinance' mode, when CMHC insurance or land transfer tax applies (e.g. down payment below 20%, first-time buyer rules), or why one would choose this over compare_mortgage_renewals. The only implied usage is the tautology that one calls it to calculate a Canadian mortgage.

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