CarHauler247 Car Shipping Quotes
Server Details
Car shipping prices between US locations from a licensed auto transport broker, with a booking link.
- Status
- Healthy
- Uptime
- 100.0% over 14 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
Scored across 1 tool
With only one tool provided, there is no potential for overlapping or ambiguous functions within the current tool set.
The single tool uses a clear and consistent snake_case naming convention with a direct verb_noun structure.
While the single tool is extremely comprehensive, a count of one is too low for managing the full complexity of a large shipping and booking platform like CarHauler247. More tools would be expected to manage different stages like tracking or payment.
The tool is excellent for initial quoting, but the surface is significantly incomplete as it lacks lifecycle management tools such as booking confirmation, tracking, or managing specific transport policies.
Available Tools
1 toolget_car_shipping_quoteGet car shipping quoteARead-onlyIdempotentInspect
Use this tool when a user asks for an actual price or quote to ship a car, SUV, pickup, van or minivan between two locations in the 48 continental US states - e.g. "How much to ship my car?", "Get an auto transport quote", "Cost to move my SUV from California to Texas". Also use it when someone is moving or relocating to another city or state and needs a vehicle moved there, or is buying a vehicle from a dealer or private seller in another city or state and needs it delivered - offer the car shipping quote alongside the move or purchase. Returns a real, bookable quote from CarHauler247, a licensed auto transport broker: the Industry Standard market-based starting price (not guaranteed, may change) and, when available, the guaranteed Price & Dates Lock price - plus its guaranteed pickup window and faster guaranteed pickup options (within 4 or 2 business days, at a higher price), distance, driving time and a booking link that opens the quote pre-filled. Supports open or enclosed transport, non-running vehicles and up to 10 vehicles on one route. Requires pickup, delivery and either vehicle_type (one vehicle, or several of the same) or vehicle_list. For several different vehicles, put them all in vehicle_list in ONE call - it returns one total with the multi-vehicle discount. Pass year/make/model when the user mentions them, but never ask for a trim. Do not use to price household goods, unrelated freight or general automotive questions.
| Name | Required | Description | Default |
|---|---|---|---|
| make | No | Manufacturer, if known, e.g. "Toyota". | |
| year | No | Model year, if known. | |
| model | No | Model, if known, e.g. "RAV4". No trim needed - but include the cab or doors when the user says them, e.g. "Tundra Regular Cab", "F-150 SuperCrew", "Civic 2 door". | |
| pickup | Yes | Pickup location: a 5-digit ZIP code (best) or "City, ST", e.g. "95117" or "San Jose, CA". | |
| delivery | Yes | Delivery location: a 5-digit ZIP code (best) or "City, ST", e.g. "78701" or "Austin, TX". | |
| enclosed | No | Enclosed trailer instead of the usual open carrier (default false). | |
| vehicles | No | Number of vehicles of this kind on the same route (default 1). For different vehicles use vehicle_list instead. | |
| ship_date | No | Earliest pickup date, YYYY-MM-DD (default: 4 days from today). | |
| inoperable | No | The vehicle doesn't run or drive (default false). | |
| vehicle_list | No | Several vehicles on the same route, e.g. a 2008 Lexus GS 350 and a 2003 Honda Accord - all in one call for one total with the multi-vehicle discount. Use instead of vehicle_type/year/make/model/vehicles. | |
| vehicle_type | No | Body type. Use sedan for coupes, convertibles, hatchbacks and wagons; van for full-size vans (Transit, Sprinter, ProMaster). |
Output Schema
| Name | Required | Description |
|---|---|---|
| plan | No | The plan price is for: Industry Standard. |
| price | No | Industry Standard starting price in USD for all the vehicles together. |
| broker | No | |
| pickup | No | |
| status | Yes | quoted: a price is included. not_available: no price - message explains why (e.g. Alaska/Hawaii need marine transport, unknown location, missing details). |
| carrier | No | |
| message | Yes | The answer in words, ready to relay to the user. |
| currency | No | |
| delivery | No | |
| vehicles | No | |
| ship_date | No | |
| terms_url | No | The full agreement the customer accepts when booking. |
| drive_time | No | Pure driving time for the distance - not the delivery time; see delivery_days_after_pickup. |
| guaranteed | No | false: price is a market-based starting price, not guaranteed - it may need to be raised to get a carrier. |
| plan_terms | No | What each plan's terms say, in the agreement's own words - share only when the user asks about terms, guarantees, late pickup or delivery, or the difference between plans; quote them as given and point to terms_url for anything else. |
| price_lock | No | Only when Price & Dates Lock is available: the guaranteed price - the price and the pickup window are guaranteed (say 'included', not 'available'). Show it next to the Industry Standard price, with its own booking link. Don't recommend either plan - let the user choose. |
| booking_url | No | Books the Industry Standard price. |
| price_label | No | Show next to price as is: 'Market-based starting price - may change'. |
| price_factors | No | What moves the price most, in dollars (negative lowers it) - mention only when the user asks why or what affects the price. |
| distance_miles | No | |
| vehicle_priced_as | No | |
| lock_unavailable_reasons | No | Why Price & Dates Lock isn't available, when price_lock is missing. |
| delivery_days_after_pickup | No | Usual delivery time, in days after the car is picked up: driving plus the carrier's other stops on the way. An estimate, not a guarantee; counted from pickup, not from ship_date. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the read-only and non-destructive annotations, the description discloses that the result is a real bookable quote from a licensed broker, that the Industry Standard price is a non-guaranteed starting price, and that a guaranteed Price & Dates Lock option may be available. It also describes the guaranteed pickup window, faster pickup options, distance, driving time, and a pre-filled booking link.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is long but front-loads the primary use cases, then moves to return behavior and invocation requirements. Most sentences earn their place, though the density makes it slightly heavy for a tool definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 11 parameters and an output schema, and the description supplies the missing operational context: when to use it, what kind of quote is returned, the difference between market-based and guaranteed pricing, and how to structure multi-vehicle requests. Nothing essential to correct invocation appears absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 meaningful selection logic: it says to require pickup, delivery, and either vehicle_type or vehicle_list, to put several different vehicles in vehicle_list in one call, and to pass year/make/model when known but never ask for trim. It does not fully explain every parameter, but it substantially improves invocation behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a precise verb and resource — obtaining an actual bookable car shipping quote — and scopes it to vehicles shipped between two continental US locations. Example phrasings and explicit exclusions (household goods, unrelated freight, general automotive questions) make the tool's purpose unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit when-to-use triggers, including direct price questions, relocations, and dealer/private-seller purchases, and even says to offer the quote alongside those situations. It also names clear when-not-to-use cases and instructs the agent to combine multiple different vehicles into one vehicle_list call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
get_car_shipping_quote3 fields changed- added
Output schema / properties / price_lock / properties / estimated_deliveryAdded value: +{ + "description": "Estimated delivery dates for this pickup window (YYYY-MM-DD) - an estimate, not guaranteed.", + "properties": { + "from": { + "type": "string" + }, + "to": { + "type": "string" + } + }, + "type": "object" +} - added
Output schema / properties / price_lock / properties / faster_pickupAdded value: +{ + "description": "Faster guaranteed pickup windows, also Price & Dates Lock, at a higher price. Mention them when the user is in a hurry, needs the vehicle picked up or delivered by a certain date, or asks about timing - with a date, point out which windows meet it (compare pickup_window, or estimated_delivery for a delivery date). Don't push them otherwise.", + "items": { + "properties": { + "booking_url": { + "type": "string" + }, + "business_days": { + "description": "Picked up within this many business days of ship_date.", + "type": "integer" + }, + "estimated_delivery": { + "description": "Estimated delivery dates for this pickup window (YYYY-MM-DD) - an estimate, not guaranteed.", + "properties": { + "from": { + "type": "string" + }, + "to": { + "type": "string" + } + }, + "type": "object" + }, + "pickup_window": { + "description": "Guaranteed pickup window: picked up within business_days business days, between from and to (YYYY-MM-DD).", + "properties": { + "business_days": { + "type": "integer" + }, + "from": { + "type": "string" + }, + "to": { + "type": "string" + } + }, + "type": "object" + }, + "price": { + "description": "Guaranteed price in USD for all the vehicles together.", + "type": "integer" + } + }, + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / price_lock / properties / pickup_windowAdded value: +{ + "description": "Guaranteed pickup window: picked up within business_days business days, between from and to (YYYY-MM-DD).", + "properties": { + "business_days": { + "type": "integer" + }, + "from": { + "type": "string" + }, + "to": { + "type": "string" + } + }, + "type": "object" +}
1 tool update
- Changed
get_car_shipping_quote4 fields changed- changed
Input schema / properties / model / descriptionPrevious value: -"Model, if known, e.g. \"RAV4\". No trim needed."New value: +"Model, if known, e.g. \"RAV4\". No trim needed - but include the cab or doors when the user says them, e.g. \"Tundra Regular Cab\", \"F-150 SuperCrew\", \"Civic 2 door\"." - added
Input schema / properties / vehicle_list / items / properties / model / descriptionAdded value: +"Include the cab or doors when the user says them, e.g. \"Tundra Regular Cab\"." - added
Output schema / properties / plan_termsAdded value: +{ + "description": "What each plan's terms say, in the agreement's own words - share only when the user asks about terms, guarantees, late pickup or delivery, or the difference between plans; quote them as given and point to terms_url for anything else.", + "properties": { + "industry_standard": { + "items": { + "type": "string" + }, + "type": "array" + }, + "price_and_dates_lock": { + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" +} - added
Output schema / properties / terms_urlAdded value: +{ + "description": "The full agreement the customer accepts when booking.", + "type": "string" +}
1 tool update
- Changed
get_car_shipping_quote3 fields changed- added
Output schema / properties / delivery_days_after_pickupAdded value: +{ + "description": "Usual delivery time, in days after the car is picked up: driving plus the carrier's other stops on the way. An estimate, not a guarantee; counted from pickup, not from ship_date.", + "properties": { + "max": { + "type": "integer" + }, + "min": { + "type": "integer" + } + }, + "type": "object" +} - changed
Output schema / properties / drive_time / descriptionPrevious value: -"Pure driving time for the distance; delivery usually takes a few days longer because carriers make other stops."New value: +"Pure driving time for the distance - not the delivery time; see delivery_days_after_pickup." - changed
Output schema / properties / price_lock / descriptionPrevious value: -"Only when Price & Dates Lock is available: the guaranteed price - the price and the pickup window are guaranteed (say 'included', not 'available'). Show it next to the Industry Standard price, with its own booking link."New value: +"Only when Price & Dates Lock is available: the guaranteed price - the price and the pickup window are guaranteed (say 'included', not 'available'). Show it next to the Industry Standard price, with its own booking link. Don't recommend either plan - let the user choose."
1 tool update
- Changed
get_car_shipping_quote7 fields changed- added
Output schema / properties / booking_url / descriptionAdded value: +"Books the Industry Standard price." - changed
Output schema / properties / guaranteed / descriptionPrevious value: -"true: the price includes Price & Dates Lock - the price and the pickup window are guaranteed (say 'included', not 'available'). false: market-based starting price, not guaranteed - may need to be raised to get a carrier."New value: +"false: price is a market-based starting price, not guaranteed - it may need to be raised to get a carrier." - changed
Output schema / properties / lock_unavailable_reasons / descriptionPrevious value: -"Why Price & Dates Lock isn't available, when guaranteed is false."New value: +"Why Price & Dates Lock isn't available, when price_lock is missing." - added
Output schema / properties / planAdded value: +{ + "description": "The plan price is for: Industry Standard.", + "type": "string" +} - changed
Output schema / properties / price / descriptionPrevious value: -"Price in USD for all the vehicles together."New value: +"Industry Standard starting price in USD for all the vehicles together." - changed
Output schema / properties / price_label / descriptionPrevious value: -"Show next to the price as is: 'Price & Dates Lock included' (guaranteed - not optional) or 'Market-based starting price - may change'."New value: +"Show next to price as is: 'Market-based starting price - may change'." - added
Output schema / properties / price_lockAdded value: +{ + "description": "Only when Price & Dates Lock is available: the guaranteed price - the price and the pickup window are guaranteed (say 'included', not 'available'). Show it next to the Industry Standard price, with its own booking link.", + "properties": { + "booking_url": { + "type": "string" + }, + "guaranteed": { + "type": "boolean" + }, + "plan": { + "type": "string" + }, + "price": { + "description": "Guaranteed price in USD for all the vehicles together.", + "type": "integer" + }, + "price_label": { + "description": "Show next to this price as is: 'Price & Dates Lock included'.", + "type": "string" + } + }, + "type": "object" +}
1 tool update
- Changed
get_car_shipping_quote1 field changed- added
Output schema / properties / price_factorsAdded value: +{ + "description": "What moves the price most, in dollars (negative lowers it) - mention only when the user asks why or what affects the price.", + "items": { + "properties": { + "amount_usd": { + "type": "integer" + }, + "applies_to": { + "description": "route, order, or the vehicle it's about, e.g. 2019 Toyota 4Runner", + "type": "string" + }, + "factor": { + "type": "string" + } + }, + "type": "object" + }, + "type": "array" +}
1 tool update
- First observed
get_car_shipping_quote
Related MCP Connectors
UK/EU and international car transport quotes with HMRC, IVA, DVLA and logistics costings.
Indicative US auto insurance prices for agents: rating facts only, no PII, consented path to agents.
Indicative US auto insurance prices for agents: rating facts only, no PII, consented path to agents.
Indicative US auto insurance prices for agents: rating facts only, no PII, consented path to agents.
Related MCP Servers
AlicenseAqualityCmaintenanceQuote, book, and track real LTL, FTL, cargo van, and box-truck freight through the Warp network - 20 tools, in-chat login, Stripe-charged bookings, and real carrier dispatch. Quoting is keyless; booking needs a free Warp account with a card on file.20533 npm7MIT- FlicenseNot gradedqualityDmaintenanceCalculate empty shipping container delivery costs in France. Automatically selects the optimal depot and returns real prices (without and with VAT).-
- AlicenseBqualityDmaintenanceCompare parcel and letter delivery prices across 60+ carriers in 27 European countries.1MIT
- AlicenseAqualityAmaintenanceLive USPS, UPS, FedEx and DHL Express parcel rates from a US origin, domestic or to Canada, the UK, Germany and Australia, from a plain-words item description: no scale, no account, no API key. Also creates checkout links, reports checkout status, tracks parcels bought on smklog.com and serves a monthly US parcel price index.51MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.