Skip to main content
Glama

Cash rebate or special APR

rebate_vs_apr
Read-onlyIdempotent

Compares a maker's cash rebate taken with the person's own loan against the maker's special APR (with any cash that combines with it): each side's payment, interest and total, the difference, the own-loan rate where the two cost the same, and the sales tax a rebate saves in states that tax the price after it. Give the amount financed before the rebate, or a vehicle price to work it out.

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": {
      "rebate": "<rebate>",
      "own_apr": "<own_apr>",
      "promo_apr": "<promo_apr>",
      "term_months": "<term_months>",
      "state": "<state>"
    },
    "name": "rebate_vs_apr"
  }
}

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
downNoCash down payment
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
rebateYesCash rebate available with your own loan or cash
doc_feeNoDoc fee; leave out to assume the state's cap, or a typical $450 where there is none
own_aprYesYour own loan APR in percent (a pre-approval)
tax_rateNoCombined sales tax rate as a decimal; leave out to use the state's rate
promo_aprYesThe maker's special APR in percent
title_regNoTitle and registration
promo_cashNoCash that combines with the special APR
term_monthsYesLoan term in months
trade_offerNoTrade-in offer
trade_payoffNoOwed on the trade-in
vehicle_priceNoVehicle price, to work out the amount financed instead
promo_term_monthsNoThe special APR's longest term, if shorter
amount_financed_before_rebateNoOut-the-door price before the rebate, less down payment and trade equity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_rate / description
      Added value: +"Combined sales tax rate as a decimal; leave out to use the state's rate"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-open-world), and the description adds genuine value by disclosing the computed outputs: per-side payment, interest and total, the difference, the break-even own-loan rate, and state-specific sales-tax savings on a rebate. It stops short of noting limitations, edge cases, or assumptions baked into the calculation.

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?

Two sentences: the first front-loads the comparison and its outputs, the second handles the key input choice. The first sentence is a long comma-chained list but each element is substantive, and there is no filler.

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 17 parameters, no output schema, and only 5 required fields, the description does the necessary work: it enumerates return values, explains the tax nuance, and covers the amount-financed-vs-price input path. Remaining gaps (defaults, what happens with partial trade data) are adequately covered by the schema itself.

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 baseline is 3. The description does add a little: 'with any cash that combines with it' clarifies promo_cash and the closing sentence explains the amount_financed_before_rebate vs. vehicle_price alternation. That is a modest lift over already complete schema text.

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 names a specific comparison verb and two well-defined resources (cash rebate vs. special APR), and enumerates what each side of the comparison yields. An agent can tell it apart from loan_payment or out_the_door by the explicit two-scenario comparison framing, though no sibling is named outright.

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?

Usage is implied rather than stated: the tool is for deciding between a rebate with outside financing and a promotional rate. The second sentence gives input guidance ('give the amount financed before the rebate, or a vehicle price to work it out') but nothing says when to prefer this over loan_payment, lease_check, or out_the_door.

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