carsearch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_carsA | Search the local historical database of collected listings with rich filters, geography and pagination. |
| search_live_marketplaceA | Run a fresh marketplace search (stores everything with history), then return matching listings from the local DB including ones seen earlier. Use for up-to-the-minute results. |
| get_listingC | Full listing record with price history, change events, description flags, vehicle link and same-vehicle candidates. |
| get_vehicleB | A physical vehicle (dedupe cluster) with all listings that were matched to it across marketplaces/time. |
| get_new_listingsB | Listings first observed since a given time (newest first). |
| get_price_historyB | Price/mileage/status snapshots and the derived summary (days on market, drops, absolute/percent change). |
| get_listing_changesC | Change events across the database (or for one listing) within a window. |
| get_comparablesB | Comparable-price analysis: sample size, median/mean/quartiles, mileage-adjusted median, manual/AWD/dealer premiums, subject percentile and methodology. Pass a listing_id OR a vehicle spec. |
| compare_carsA | Side-by-side comparison of several listings: key facts, comps position, project score, deal signals and description risk flags. |
| find_dealsA | Rank listings by deal signals and/or project-car score: comps position, price drops, time on market, seller, description risk flags — each item carries reasons, risks, risk_flags, project_score. Use sort_by='project' + a profile to answer 'best project cars'. |
| find_price_dropsB | Listings whose asking price dropped by >= min_pct within the window (single or cumulative drops). |
| find_long_sitting_listingsC | Active listings on the market for at least min_days (optionally with several price cuts). |
| analyze_listingB | Everything about one listing: full record, price history, description risk/positive flags with evidence, comparables, project-car score with component explanations, deal signals. |
| score_listingC | Project-car score (0-100) with per-component scores/weights/explanations under a named or custom profile. |
| analyze_marketC | Market analytics: median prices over time / by mileage / by group, manual & AWD premiums, dealer vs private, cheapening models, turnover, long-sitting. |
| list_saved_searchesB | Saved (monitored) searches with schedule state. |
| create_saved_searchB | Create or update a saved search that the scheduler reruns; alerts fire on new matches, price drops, deals. |
| run_saved_searchA | Run a saved search now: crawls incrementally, returns new listings (with deal/project scores) and any alerts triggered. |
| delete_saved_searchB | Delete a saved search. |
| get_alertsC | Recent alerts (new matches, price drops, target price, rare manuals, deal scores) with reasons. |
| get_statusB | Collector health: DB counts by source/province, recent runs, HTTP metrics, provider capabilities. |
| get_generation_codesA | Supported generation/chassis labels per make/model (for the |
| analyze_listing_imagesA | Cache the listing's photos (sha256 + perceptual hash) and run the pluggable vision backend (checklist: rust, rockers, paint mismatch, damage, interior, warning lights, mods, tires, stance, engine bay). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Each tool targets a distinct resource or analytical mode: search vs. live search, listing vs. vehicle vs. price history vs. changes, comparables vs. comparison vs. market analysis. Even the find_* tools are separated by clear signals (deals, price drops, long-sitting), so an agent should be able to select the right tool confidently.
Tool names consistently follow a snake_case verb_noun pattern: search_cars, get_listing, find_deals, analyze_listing, list_saved_searches, delete_saved_search. Minor variations like search_live_marketplace or analyze_listing_images remain readable and fit the same convention.
At 23 tools, the server is on the heavy side and falls into the 16-25 range that feels dense. The broad car-search/analysis domain justifies many of them, but the overall surface could be streamlined or grouped further.
The tool surface covers the full workflow: historical and live search, listing/vehicle detail, price history and changes, comparables, market analytics, image/listing analysis, scoring, saved-search lifecycle, and alert retrieval. Saved searches support create/update, run, list, and delete, so there are no obvious dead ends for the stated domain.