Skip to main content
Glama

get_payment_estimate

Use this to answer 'what would my monthly payment be' for ONE listing. It runs the same itemized out-the-door calculation as estimate_out_the_door (always treated as financed) and turns it into a DEMO monthly finance payment: out-the-door total minus down payment and trade equity, amortized at the APR (or a demo APR by credit_tier) over term_months. Returns finance.estimated_monthly_payment rounded to $5 with monthly_payment_unrounded, monthly_payment_range (rounded outward, so it always contains the unrounded value), financing_eligibility (demo lender rules: minimum amount financed, max term by vehicle age and mileage, with flags), amount_financed_estimate, total_of_payments, finance_charge and every assumption, plus the out-the-door figure it used, a one-line assumptions_summary and any dealer-advertised payment shown separately (not comparable unless the terms match). Totals: total_cost_including_trade_equity (PRIMARY: cash down plus payments plus net trade equity given up) and cash_outlay_excluding_trade_equity (cash down plus payments); total_cost_estimate is a deprecated alias of the latter, kept for one version. For ONE set of terms only: to compare two or more down, term, trade or credit options, call compare_payment_scenarios once instead of calling this tool repeatedly. Use get_price_breakdown instead for the dealer's listed price and fees only, and estimate_out_the_door for the full itemized total without a payment. To find cars by payment across many listings, use search_inventory with max_monthly_payment (canonical; payment_max is a deprecated alias). Estimate, not an offer; dealer sets price, lender sets rate. Not penny-accurate. Leases are not modeled.

Input Schema

NameRequiredDescriptionDefault
aprNoAPR percent, 0 to 36. If omitted, a demo APR is picked by credit_tier.
payoffNoLoan payoff owed on the trade-in, USD (negative equity is added to the amount financed).
buyer_zipNoBuyer's five-digit ZIP. Alone it resolves buyer state, county and city (echoed in tax_location.resolution with the source).
buyer_cityNoBuyer's city, for local tax lines.
listing_idYesdealer_key:VIN from search_inventory.
buyer_stateNoBuyer's two-letter state for tax and fees. Default: the selling store's state, or the state of buyer_zip.
credit_tierNoexcellent, good (default), fair or poor. Picks the demo APR when apr is omitted (used and cpo rates are higher than new).
term_monthsNoLoan term in months, 12 to 96. Default 60.
trade_valueNoTrade-in allowance in USD. Passed to the out-the-door step, so it gets the state's trade-in tax credit where allowed.
buyer_countyNoBuyer's county without 'County', for local tax lines.
down_paymentNoCash down in USD, subtracted from the out-the-door total. Default 0.
trade_equityNoNet trade equity in USD when allowance and payoff are unknown (negative if upside down). Subtracted after tax, so no trade-in tax credit is applied.
eligible_incentive_labelsNolabel_raw values of conditional incentives from get_price_breakdown that the buyer qualifies for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / buyer_zip / description
      Previous value: -"Buyer's five-digit ZIP. Here it sets buyer state and city when buyer_state is omitted."New value: +"Buyer's five-digit ZIP. Alone it resolves buyer state, county and city (echoed in tax_location.resolution with the source)."
  2. Changed11 schema fields changed
    • changedInput schema / properties / apr / description
      Previous value: -"APR percent. If omitted, a demo APR by credit_tier is used."New value: +"APR percent, 0 to 36. If omitted, a demo APR is picked by credit_tier."
    • changedInput schema / properties / buyer_city / description
      Previous value: -"Buyer's city."New value: +"Buyer's city, for local tax lines."
    • changedInput schema / properties / buyer_county / description
      Previous value: -"Buyer's county without 'County'."New value: +"Buyer's county without 'County', for local tax lines."
    • changedInput schema / properties / buyer_state / description
      Previous value: -"Buyer's two-letter state. Default: the selling store's state."New value: +"Buyer's two-letter state for tax and fees. Default: the selling store's state, or the state of buyer_zip."
    • changedInput schema / properties / buyer_zip / description
      Previous value: -"Buyer's five-digit ZIP; sets state and city when buyer_state is omitted."New value: +"Buyer's five-digit ZIP. Here it sets buyer state and city when buyer_state is omitted."
    • changedInput schema / properties / credit_tier / description
      Previous value: -"excellent, good (default), fair or poor."New value: +"excellent, good (default), fair or poor. Picks the demo APR when apr is omitted (used and cpo rates are higher than new)."
    • changedInput schema / properties / down_payment / description
      Previous value: -"Cash down in USD. Default 0."New value: +"Cash down in USD, subtracted from the out-the-door total. Default 0."
    • changedInput schema / properties / eligible_incentive_labels / description
      Previous value: -"Conditional incentive label_raw values the buyer qualifies for."New value: +"label_raw values of conditional incentives from get_price_breakdown that the buyer qualifies for."
    • changedInput schema / properties / payoff / description
      Previous value: -"Loan payoff owed on the trade-in, USD."New value: +"Loan payoff owed on the trade-in, USD (negative equity is added to the amount financed)."
    • changedInput schema / properties / trade_equity / description
      Previous value: -"Net trade equity in USD when allowance and payoff are unknown; no tax credit applied."New value: +"Net trade equity in USD when allowance and payoff are unknown (negative if upside down). Subtracted after tax, so no trade-in tax credit is applied."
    • changedInput schema / properties / trade_value / description
      Previous value: -"Trade-in allowance in USD."New value: +"Trade-in allowance in USD. Passed to the out-the-door step, so it gets the state's trade-in tax credit where allowed."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, but the description discloses the calculation path, demo APR behavior by credit_tier, $5 rounding and range semantics, demo lender eligibility flags, assumptions, deprecated aliases, and the 'estimate, not offer' limitation. This is strong behavioral disclosure for a tool without annotations.

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?

Purpose and routing guidance are front-loaded, and the length is justified by the complex calculation and lack of an output schema. The second sentence is dense, but most details earn their place.

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?

With no annotations and no output schema, the description still explains return fields, assumptions, total-cost metrics, a deprecated alias, and key limitations such as leases not being modeled. It gives an agent enough context to invoke and interpret the tool correctly.

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 all 13 parameters are already documented in the schema. The description adds useful context about parameter interaction—down payment and trade equity reduce the financed amount, APR or demo APR is selected by credit_tier—but this is largely redundant with the schema, so the baseline 3 is appropriate.

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?

The description opens with the exact user question and resource: 'what would my monthly payment be' for ONE listing. It clearly distinguishes the tool from estimate_out_the_door, get_price_breakdown, compare_payment_scenarios, and search_inventory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly limits use to ONE set of terms and directs agents to compare_payment_scenarios for multiple down, term, trade, or credit options. It also names alternatives for dealer price/fees, out-the-door totals without payment, and finding cars by payment across listings.

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