Trim & Spec Stocking Matrix
Which trims, drivetrains, colours and transmissions of a nameplate sell in your state, at what price and odometer, how fast.
This is the technical reference. For the price, a rendered sample and answers to common questions, see the Trim & Spec Stocking Matrix product page.
At a glance
| Price | $2.99 per run. |
| Tool name | generate_trim_spec_stocking_matrix |
| Scope | reports:trim-spec-stocking-matrix |
| Built for | Small Dealer, Dealer Group |
What it does
The stocking matrix for one nameplate (make and model) in one US state over a window of whole months (3 by default, up to 12): four ranked tables, by trim, drivetrain, exterior colour and transmission, each row with the units that left dealer websites, its share of the nameplate, the Low end, median and High end of the advertised asking price at exit, the median odometer and the median days to sell. Price and odometer sit on the same row on purpose: a top trim that reads cheap because it sold at high mileage is named, with both numbers. Closes with the stocking call: the five trims to stock by volume with their price and odometer, the three slowest to turn, the drivetrain, colour and transmission mix to hold, and the one read that matters most. Units and shares add across the window; the medians describe the latest month with 5 or more priced sales and are never averaged across months. From the Sold Summary API: a sale is inferred when a listing leaves a dealer website, every price is the advertised asking price at exit (never a negotiated transaction price), and the data runs through the latest complete month. Use when a dealer, buyer or dealer group asks WHICH trims, specs or colours of a nameplate to stock in a state, what each sells for and how fast, or whether a cheap-looking trim is really cheap. Do NOT use to pick nameplates without one in mind (use Market Movers), to set a max bid around a ZIP (use Stocking Guide, which prices reconditioning and margin), or to time the buying (use Seasonal Buy-Sell Calendar). The sold data has state grain, not ZIP or radius; a ZIP is read as its state. PRICING: $2.99 per run.
Arguments
| Argument | What it is | Example | |
|---|---|---|---|
make |
Required | Make of the nameplate (e.g. Toyota). | Toyota |
model |
Required | Model of the nameplate (e.g. RAV4). | RAV4 |
state |
Required | US state, as a 2-letter code (e.g. TX). A 5-digit ZIP is read as its state. The sold data has state and city grain only, no ZIP or radius. | TX |
inventory_type |
Recommended | Which market: used (the default), new, or certified pre-owned. | used |
months |
Recommended | Whole months to count units over, ending at the latest data month: 3 by default, 1 to 12. The medians always describe one month. | 3 |
What comes back
- Trims that sold: units over the window, share of the nameplate, the Low end, median and High end of the asking price at exit, the median odometer and the days to sell, on the same row
- Drivetrains, exterior colours and transmissions that sold, ranked the same way
- What to stock: the five trims by volume with their price and odometer, the three slowest to turn, and the spec mix to hold
- The read that matters: a trim that only looks cheap because it sold at high mileage, named with both numbers
- Key metrics: units sold, top trim, the nameplate median price, odometer and days to sell, and the data window
- Next steps: a Stocking Guide for the max bid by ZIP, the Seasonal Buy-Sell Calendar for timing, and a monthly monitor
Asking for it in a chat client
Which RAV4 trims and colours should I stock in Texas?
Show the trim and spec mix of used F-150s selling in Florida
Running it from a backend
Grant an agent the reports:trim-spec-stocking-matrix scope, then call the tool over MCP:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "generate_trim_spec_stocking_matrix",
"arguments": {
"make": "Toyota",
"model": "RAV4",
"state": "TX",
"inventory_type": "used",
"months": 3
}
}
}
See Server-side access for the token exchange and how to read the response.