Skip to main content
Glama

CarLoanMath

Auto loan amortization schedule

amortization_schedule
Read-onlyIdempotent

Principal, interest and remaining balance over the life of one loan. Yearly summary by default; period 'month' gives every payment (up to 120 rows). When optional inputs are omitted, the result includes assumed_defaults (the values actually used) and a short text line so you can call again with those parameters. assumed_defaults is omitted when every optional input was provided.

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>",
      "apr": "<apr>",
      "term_months": "<term_months>"
    },
    "name": "amortization_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
aprYesYearly interest rate in percent, compounded monthly (the same number as the site’s rate field), e.g. 6.5 for 6.5%. A lender’s APR can be a little higher because it folds in some fees. Use 0 for 0% financing.
downNoCash down payment in USD. Default 0.
feesNoTitle, registration, documentation and dealer fees in USD. Default 0.
priceYesVehicle price in USD (before tax, fees, down payment and trade-in).
periodNo'year' (default) or 'month'.
countryNoCountry of the purchase, ISO 3166-1 alpha-2. Default "US". Only US is available for now.US
trade_inNoTrade-in value in USD credited against the price. Default 0.
term_monthsYesLoan term in whole months, 1–120 (common: 36, 48, 60, 72, 84).
sales_tax_rateNoSales tax in percent of the vehicle price, e.g. 7 for 7%. No state rules or trade-in tax credit are applied. Default 0.
owed_on_trade_inNoLoan balance still owed on the trade-in, rolled into the new loan (negative equity). Default 0.
tax_and_fees_financedNofalse (default, the site's "Pay upfront"): sales tax and fees are paid in cash at purchase, not financed. true: they are added to the loan.

Output Schema

NameRequiredDescriptionDefault
inputsYes
periodYes
countryYes
scheduleYes
sales_taxYes
share_urlYes
disclaimerYes
total_costYes
total_interestYes
amount_financedYes
monthly_paymentYes
assumed_defaultsNoOptional inputs the caller omitted, with the values actually used. The field is omitted when nothing was assumed.
total_of_paymentsYes
cash_due_at_purchaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the bar is lower. The description adds genuinely new behavioral detail beyond them: the 120-row cap on monthly output and the assumed_defaults echo (with a text line for re-calling) that appears only when optional inputs are omitted and is suppressed otherwise.

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 tight sentences: what it returns, the default granularity and its cap, then the default-echo contract. Nothing is padded and the most important scoping facts come first.

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 eleven parameters, full schema descriptions, and an output schema, the description only needs to cover behavior the structures cannot express, which it does for granularity and default echoing. Minor gaps remain: no note on whether taxes/fees or negative equity are already reflected, though the schema hints at these.

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 coverage is 100%, so the schema already defines all eleven parameters, including units, ranges, and defaults. The description adds the period enum's practical consequence and how omitted optional inputs are resolved via assumed_defaults, which is a modest increment over the schema rather than a substantive one, so baseline-plus is appropriate.

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 states a specific resource and output shape: principal, interest, and remaining balance across the life of a single loan. That is clearly a schedule rather than a one-off payment quote, distinguishing it implicitly from calculate_auto_loan, but no sibling is named explicitly.

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?

It explains the period switch (yearly summary default vs. 'month' for every payment, capped at 120 rows), which is useful selection guidance among modes. However, it never says when to use this tool rather than compare_auto_loans or calculate_auto_loan, so cross-tool routing is left to inference.

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