Skip to main content
Glama

Check a lease

lease_check
Read-onlyIdempotent

Works a lease quote from the MSRP, selling price, residual and money factor (or the lease's APR): the depreciation and rent charges, the monthly payment with the state's lease tax, the money factor as an APR, and the total cost, including any tax charged once at the start (Texas, Ohio and others). With a loan APR and term, it also compares leasing with buying the same car over the lease's months. Use it to check a lease offer's numbers; for buying, use out_the_door.

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": {
      "msrp": "<msrp>",
      "selling_price": "<selling_price>",
      "residual_percent": "<residual_percent>",
      "term_months": "<term_months>",
      "state": "<state>"
    },
    "name": "lease_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or county in the state's rate table (23 states; state_rules says which), like Pittsburgh or Allegheny County: sets the combined rate from the state's own rate file. Where a city is in several counties (Chicago, Milwaukee), give county too. A place name only, never an address or ZIP
feesNoAcquisition and other fees rolled into the lease
msrpYesMSRP (sticker price)
stateYesTwo-letter state code (DC included), like PA
countyNoCounty from the state's list (Pennsylvania, Nevada, Wisconsin; state_rules lists them), like Allegheny County: sets the combined rate. A county name only, never an address or ZIP
buy_aprNoA loan APR, to compare with buying
doc_feeNoDoc fee when buying, for the estimated out-the-door; leave out to assume the state's cap, or a typical $450 where there is none
buy_downNoDown payment when buying
tax_rateNoCombined sales tax rate as a decimal (state and local); leave out to use the state's rate. A state lease tax (Pennsylvania's 3%) is added on top either way; Alabama's and West Virginia's own lease-payment rates replace their state sales rate; where the state taxes a lease once at the start (Texas, Ohio), this is that tax's rate and the payments carry none
lease_aprNoThe lease's rate as an APR, instead of the money factor
term_monthsYesLease term in months
money_factorNoMoney factor, e.g. 0.0025
selling_priceYesThe negotiated price the lease is built on
due_at_signingNoCash down, lease rebates and trade equity that lower the price
buy_term_monthsNoLoan term, to compare with buying
disposition_feeNoTurn-in fee at the end
buy_out_the_doorNoOut-the-door price when buying; leave out to estimate it
residual_percentYesResidual as a percent of MSRP (58 for 58%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent calculator. The description adds meaningful behavioral context beyond annotations by listing computed outputs and explaining state-specific lease-tax timing, such as taxes charged once at the start in Texas and Ohio. It stops short of detailing output format or edge-case handling, so it is strong but not exhaustive.

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?

The description is front-loaded with the core action and uses a colon list to pack the computed outputs without filler. Its length is appropriate for an 18-parameter lease calculator and every clause contributes useful scope or behavior.

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 a complex 18-parameter tool with no output schema, the description explains the calculated return values, state tax nuances, and optional lease-vs-buy comparison. The schema carries parameter-level detail, and the description names the relevant sibling alternative out_the_door, leaving no major gaps for correct invocation.

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 the schema already documents all 18 parameters thoroughly. The description reinforces core inputs like MSRP, selling price, residual, money factor or lease APR, and the optional buy APR and term, but it does not add parameter semantics beyond what the schema provides.

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 states a specific action: it works a lease quote from MSRP, selling price, residual, and money factor or lease APR, and returns depreciation, rent charges, monthly payment, APR equivalent, and total cost. It explicitly distinguishes lease checking from buying by naming out_the_door as the alternative.

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 gives a direct usage rule: use this to check a lease offer's numbers, and for buying use out_the_door. The optional lease-vs-buy comparison is also clearly conditioned on supplying a loan APR and term.

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