Skip to main content
Glama

carmax_get_instant_offer

Get an instant cash offer for selling your car by providing a VIN or license plate and state; returns an estimated offer range and next steps.

Instructions

Get an instant cash offer from CarMax for selling your car. Provide VIN or license plate + state. Returns estimated offer range and next steps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "carmax_get_instant_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinNoVehicle Identification Number (17 characters)
zipNoZIP code for the offer (affects offer amount)
stateNo2-letter US state code for the license plate (e.g., 'CA', 'TX')
mileageNoCurrent odometer reading in miles
license_plateNoLicense plate number (used if VIN not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the result is an estimated offer range plus next steps, but it does not mention whether the offer is binding, whether authentication is required, or any rate limits.

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 short sentences, front-loaded with purpose, followed by input requirements and return summary. There is no wasted text.

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?

The description covers purpose, key input condition, and return content, which is adequate given full schema coverage and no output schema. Minor gaps remain around alternative-tool routing and offer binding/auth details.

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 five parameters. The description restates the VIN-or-license-plate+state condition that is already present in the schema and omits the roles of zip and mileage, so it adds limited value beyond structured fields.

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 states a specific verb and resource: get an instant cash offer from CarMax for selling a car. It clearly distinguishes itself by naming the provider, though it does not explicitly contrast with the sibling carvana_get_offer or other alternatives.

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

Usage Guidelines4/5

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

It gives clear usage context ('for selling your car') and input guidance ('Provide VIN or license plate + state'), but does not state when to choose this over sibling tools such as carvana_get_offer or carmax_get_vehicle_details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.