Skip to main content
Glama

ExoticCar.Loans: exotic and classic car loan calculator

Compare terms and balloons for one car

compare_exotic_car_loan_terms
Read-onlyIdempotent

Side-by-side payment, total interest, balloon and underwater stretch for 2 to 6 term and balloon combinations on the same car, price, down payment and APR (for example 120 vs 180 months, or 0% vs 30% balloon), using the exoticcar.loans calculator math.

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>",
      "options": "<options>"
    },
    "name": "compare_exotic_car_loan_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
aprYesAPR in percent from the borrower's own quote, e.g. 8.5. This server has no rate of its own.
downNoDown payment in dollars. Default 0.
modelNoDepreciation preset from https://exoticcar.loans/depreciation/ (annualized published figure). Default "all-vehicles" (iSeeCars all-vehicle benchmark). Ignored when value_change_pct is given.
priceYesPurchase price in US dollars, e.g. 250000.
optionsYesTerm and balloon combinations, e.g. [{"months":120},{"months":180},{"months":120,"balloon_pct":30}].
finance_taxNoRoll the sales tax into the loan (true, default) or pay it at signing (false).
sales_tax_pctNoSales tax rate in percent. Default 0.
value_change_pctNoYour own expected change in the car's value per year, percent; negative = losing value (e.g. -5). Overrides model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real value beyond that by naming the computed outputs (payment, total interest, balloon, underwater stretch) even though no output schema exists, and by anchoring the results to exoticcar.loans calculator math. It doesn't mention failure modes for invalid option combos, so it isn't a 5.

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?

One sentence, front-loaded with the comparison verb and the four returned metrics, with zero filler. It is a long, clause-heavy sentence that takes a second pass to parse fully, which keeps it from a 5.

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

Completeness5/5

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

For an 8-parameter tool with full schema coverage, rich annotations and no output schema, the description supplies the missing piece — what the comparison actually returns — plus the domain anchor for the math. Nothing an agent needs to select or invoke it correctly is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description earns above that by making explicit that price, down payment and APR are held constant across all options and only term/balloon vary — a semantic constraint on how the options array is interpreted that the schema alone states only indirectly.

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?

Names a specific verb (compare) and resource (payment, total interest, balloon, underwater stretch) with explicit scope: 2 to 6 term and balloon combinations on the same car. The examples ("120 vs 180 months, or 0% vs 30% balloon") make it unmistakable against the sibling calculate_exotic_car_loan, which handles a single scenario.

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?

The description gives concrete situations that call for this tool (comparing two terms, or 0% vs 30% balloon), which is strong positive guidance. It stops short of stating when not to use it or naming calculate_exotic_car_loan as the alternative for a single quote, so the routing is inferable rather than explicit.

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