Skip to main content
Glama

Check a dealer's quote

check_quote
Read-onlyIdempotent

Reads a dealer's out-the-door quote, pasted as text (up to 8 KB) or given as line items, and checks it line by line: the out-the-door total, the doc fee against the state's cap (and capped service fees such as Ohio's $50 convenience fee), the tax line against the state's rate, finance-office add-ons with typical prices, the trade allowance against written trade-in offers, the trade equity and amount financed, and the walk line. Lines with an email address or phone number are removed before reading and never returned. Nothing is stored.

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": {
      "state": "<state>"
    },
    "name": "check_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe quote as pasted (an email or a buyer's order). Leave out to send lines instead.
linesNoThe quote as line items, instead of text (its add-ons go in add_ons)
stateYesTwo-letter state code (DC included), like PA
add_onsNoWith lines: the dealer add-ons and their prices (paint protection, VIN etching, a service contract)
tax_rateNoCombined sales tax rate as a decimal; leave out to use the state's rate
walk_lineNoThe walk line, out the door
trade_offersNoWritten trade-in offers, to compare the best open one with the allowance
trade_allowanceNoThe trade-in allowance on the quote, when sending lines (read from text otherwise)
best_trade_offerNoThe best written trade-in offer still open (CarMax, Carvana...), to compare with the allowance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / add_ons
      Added value: +{
      +  "description": "With lines: the dealer add-ons and their prices (paint protection, VIN etching, a service contract)",
      +  "items": {
      +    "properties": {
      +      "amount": {
      +        "description": "Its price",
      +        "maximum": 100000,
      +        "minimum": 0,
      +        "type": "number"
      +      },
      +      "name": {
      +        "description": "What the dealer calls the add-on",
      +        "maxLength": 60,
      +        "minLength": 1,
      +        "pattern": "^[^\\r\\n]*$",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "amount"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 12,
      +  "type": "array"
      +}
    • addedInput schema / properties / lines / additionalProperties
      Added value: +false
    • changedInput schema / properties / lines / description
      Previous value: -"The quote as line items, instead of text"New value: +"The quote as line items, instead of text (its add-ons go in add_ons)"
    • removedInput schema / properties / lines / properties / add_ons
      Removed value: -{
      -  "default": [],
      -  "description": "Dealer add-ons and their prices (paint protection, VIN etching, a service contract)",
      -  "items": {
      -    "properties": {
      -      "amount": {
      -        "description": "Its price",
      -        "maximum": 100000,
      -        "minimum": 0,
      -        "type": "number"
      -      },
      -      "name": {
      -        "description": "What the dealer calls the add-on",
      -        "maxLength": 60,
      -        "minLength": 1,
      -        "pattern": "^[^\\r\\n]*$",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name",
      -      "amount"
      -    ],
      -    "type": "object"
      -  },
      -  "maxItems": 12,
      -  "type": "array"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / lines / properties / add_ons / description
      Added value: +"Dealer add-ons and their prices (paint protection, VIN etching, a service contract)"
  3. 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 read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: PII such as email addresses and phone numbers is removed before reading and never returned, and nothing is stored. It does not describe the response structure, but the privacy and storage behavior is unusually well disclosed.

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?

The description is a single dense sentence, but it is front-loaded and structured around the reading-and-checking workflow. Every clause names a concrete check or constraint, though the long enumeration is slightly harder to scan than a short bulleted structure.

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

Completeness3/5

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

This is a complex tool with nine parameters, nested objects, and no output schema, so the description should ideally explain what the check returns. It covers input modes, privacy handling, and the line-by-line checks well, but it leaves the return format and error behavior unspecified.

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%, and the nested schema already documents each parameter in detail. The description reinforces that the quote can be pasted text up to 8 KB or sent as line items, and it mentions several checked fields, but it adds little syntax or format detail beyond the schema.

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 gives a specific verb and resource: it reads a dealer's out-the-door quote and checks it line by line. It enumerates the checks performed, including doc fee caps, tax, add-ons, trade allowance, and walk line, so the agent can distinguish this from siblings like compare_quotes or lease_check.

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?

The description makes the usage context clear: checking a pasted quote or a structured set of line items. However, it does not explicitly say when to use this tool versus compare_quotes, out_the_door, or lease_check, nor does it state when not to use it.

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