Skip to main content
Glama

Compare dealer quotes

compare_quotes
Read-onlyIdempotent

Ranks two to ten itemized dealer quotes for the same car by out-the-door total, with each one's gap to the lowest and to the walk line, and (with a state) each doc fee against the state's cap. Use it once several dealers have quoted; to read one quote line by line, use check_quote. Returns the ranking and a planner link with the quotes filled in.

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": {
      "quotes": "<quotes>"
    },
    "name": "compare_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state code (DC included), like PA
quotesYesEach dealer's quote as line items: price, rebates, doc fee, tax and fees (the add-ons go in add_ons)
add_onsNoEvery quote's dealer add-ons (paint protection, VIN etching, a service contract), each with the number of the quote it is on
walk_lineNoThe walk line, out the door

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / add_ons
      Added value: +{
      +  "description": "Every quote's dealer add-ons (paint protection, VIN etching, a service contract), each with the number of the quote it is on",
      +  "items": {
      +    "additionalProperties": false,
      +    "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"
      +      },
      +      "quote": {
      +        "description": "Which quote it is on: 1 for the first in quotes, 2 for the second",
      +        "maximum": 10,
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "quote",
      +      "name",
      +      "amount"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 120,
      +  "type": "array"
      +}
    • changedInput schema / properties / quotes / description
      Previous value: -"Each dealer's quote as line items: price, rebates, doc fee, add-ons, tax and fees"New value: +"Each dealer's quote as line items: price, rebates, doc fee, tax and fees (the add-ons go in add_ons)"
    • addedInput schema / properties / quotes / items / additionalProperties
      Added value: +false
    • removedInput schema / properties / quotes / items / 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. Changed2 schema fields changed
    • addedInput schema / properties / quotes / description
      Added value: +"Each dealer's quote as line items: price, rebates, doc fee, add-ons, tax and fees"
    • addedInput schema / properties / quotes / items / properties / add_ons / description
      Added value: +"Dealer add-ons and their prices (paint protection, VIN etching, a service contract)"
  3. First observed

TDQS

A4.6/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-destructive), and the description adds real behavior beyond them: the exact comparison outputs (gap to lowest, gap to walk line, doc fee vs. state cap), the conditional effect of supplying a state, and the returned planner link. It does not discuss edge cases like tied totals or invalid quote counts, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, no filler, with the core action and scope front-loaded before the sibling routing and the return summary. Every clause carries information an agent needs.

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 no output schema, the description still summarizes what comes back (a ranking plus a filled-in planner link) and covers the input envelope (2–10 quotes, optional state). Minor gap: it does not describe the ranking output's shape or how add-ons affect the total, though the schema handles the input side.

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, but the description adds meaning the schema does not: it explains that 'state' activates doc-fee cap comparison and that 'walk_line' is the out-the-door threshold used for the gap calculation. That connects two of the four parameters to observable output rather than just restating field names.

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?

States a specific verb and resource ('Ranks two to ten itemized dealer quotes for the same car') plus the ranking basis (out-the-door total), and explicitly contrasts itself with check_quote. An agent can distinguish it from every sibling without opening the schema.

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?

Gives an explicit trigger ('Use it once several dealers have quoted') and names the alternative for the other case ('to read one quote line by line, use check_quote'). Both the when and the when-not are stated, not inferred.

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