Skip to main content
Glama
UseCOS MCP Server

UseCOS MCP Server

by rivlosys

calculate_canadian_auto_loan

Calculate Canadian auto loan monthly payments, provincial sales tax after trade-in, net trade-in equity, and total interest from vehicle price and annual rate.

Instructions

Calculate Canadian auto loan monthly payment, provincial sales tax after trade-in, net trade-in equity, and total interest.

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": {
      "vehiclePrice": "<vehiclePrice>",
      "annualRatePercent": "<annualRatePercent>"
    },
    "name": "calculate_canadian_auto_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
feesNo
rebateNo
termMonthsNo
downPaymentNo
tradeInValueNo
vehiclePriceYes
taxRatePercentNo
annualRatePercentYes
amountOwingOnTradeNo

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 supplied, the description carries the full burden, but for a pure side-effect-free calculation the burden is small. It does add genuinely useful behavior: sales tax is computed 'after trade-in' (i.e., the taxable base is reduced by trade-in) and 'net trade-in equity' is reported, which implies tradeInValue minus amountOwingOnTrade. It does not state assumptions such as rounding, whether rebates reduce the taxable base, or the unit convention for rate inputs.

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 front-loaded sentence with no filler; every clause names a distinct computed output. It could have been structured as a short list, but no wording is wasted.

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 9-parameter calculation with no annotations and no output schema, the description helpfully enumerates the four results, effectively doubling as a return-value summary. However, it leaves most input parameters and the calculation assumptions undocumented, so an agent cannot fully predict how fees, rebate, or downPayment feed into the results.

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 0% across 9 parameters, so the description must compensate and it only partially does. It clarifies the treatment of tradeInValue (tax after trade-in, net equity) but says nothing about fees, rebate, downPayment, termMonths default of 60, or whether annualRatePercent/taxRatePercent are whole percentages versus decimals. Names alone carry most of the meaning for the remaining parameters.

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?

States a specific verb ('Calculate') and a specific resource ('Canadian auto loan'), then enumerates the four computed outputs (monthly payment, provincial sales tax after trade-in, net trade-in equity, total interest). The domain ('Canadian auto loan') inherently separates it from siblings like calculate_canadian_mortgage or calculate_canadian_paycheck, though the description never explicitly says so.

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, no statement of prerequisites, and no mention of alternatives. An agent can infer from the name that this is for Canadian auto loans, but nothing in the text tells it when this tool is the right choice versus the mortgage or paycheck calculators.

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