Vehicle options module — JetSetGo MCP reference

The vehicleoptions module manages four vehicle-booking configuration tables: attachment options (add-ons extending a vehicle's dimensions), towing options, hire vehicle categories, and custom ("other") vehicle configurations. It exposes create-read-update-delete access to these reference records through the JetSetGo MCP server.

What the operator uses it for

Operators maintain the catalogues describing what can be attached to, towed by, or hired as a vehicle. Attachment options are dimension extenders such as bull bars or roof racks, carrying the length and height they add. Towing options describe trailers and other towed vehicles, linked to a product sub-type. Hire options define rental vehicle categories with full dimensions, weight, an icon, and an electric-vehicle question flag. Other vehicle options cover custom vehicle types (for example trucks or buses) with per-dimension suggestion-or-maximum ranges and flags controlling which measurements a traveller provides.

Through the module's tools an assistant can list or fetch any of the four record types on request and, after explicit preview and confirmation, create, update, or delete them.

Where it sits

The module is pure configuration over four reference tables in the shared reference schema, accessed via generated CRUD operations. Its only upstream dependency is product-types: towing, hire, and custom-vehicle records carry a product sub-type id owned there, resolved to names at runtime. Downstream, bookings, pricing, and inventory consume these records when fitting quotes and vehicles, though the module performs no reference checks.

Unlike provision-gated modules, vehicleoptions is always enabled wherever the MCP server runs.

Key concepts

Attachment option — a vehicle add-on extending booked dimensions; carries name, icon, added length and height.
Towing option — a trailer or towed vehicle type linked to a product sub-type.
Hire option — a rental vehicle category with dimensions, weight, and an electric-vehicle question flag.
Other vehicle option — a custom vehicle configuration with 20+ fields including min/max ranges per dimension.
ask_* flags — booleans controlling which measurements a traveller is prompted for on hire and custom vehicles.
Dimension units — lengths/widths/heights in millimetres (0–50000); weight in tonnes (0–100).
Hard delete — deletes remove the row outright; no soft-delete or archive state.
Guarded write — writes first return a preview of current state plus intended change, then apply only after confirmation with a matching token.

Tools

Tool names are assembled from small per-entity factories (a list/get pair for reads, save/delete pairs for writes, across four entity types), so they may not appear as literal strings in source. Sixteen tools ship in total.

Tool	Class	Purpose
`vehicleoptions_list_attachment_options`	Read	List all attachment options.
`vehicleoptions_get_attachment_option`	Read	Fetch one attachment option by id.
`vehicleoptions_list_towing_options`	Read	List all towing options.
`vehicleoptions_get_towing_option`	Read	Fetch one towing option by id.
`vehicleoptions_list_hire_options`	Read	List all hire vehicle categories.
`vehicleoptions_get_hire_option`	Read	Fetch one hire option by id.
`vehicleoptions_list_other_vehicle_options`	Read	List all custom vehicle configurations.
`vehicleoptions_get_other_vehicle_option`	Read	Fetch one custom vehicle configuration by id.
`vehicleoptions_save_attachment_option`	Guarded write	Create or update an attachment option.
`vehicleoptions_delete_attachment_option`	Guarded write	Hard-delete an attachment option by id.
`vehicleoptions_save_towing_option`	Guarded write	Create or update a towing option.
`vehicleoptions_delete_towing_option`	Guarded write	Hard-delete a towing option by id.
`vehicleoptions_save_hire_option`	Guarded write	Create or update a hire vehicle category.
`vehicleoptions_delete_hire_option`	Guarded write	Hard-delete a hire option by id.
`vehicleoptions_save_other_vehicle_option`	Guarded write	Create or update a custom vehicle configuration.
`vehicleoptions_delete_other_vehicle_option`	Guarded write	Hard-delete a custom vehicle configuration by id.

Rules worth knowing

Writes require an explicit tenant. Every write tool rejects a request that does not name the tenant; reads default to the session tenant when omitted.
Save is upsert-shaped. Omitting id creates; supplying id updates only the fields provided, after re-reading current state for the preview.
Deletes are destructive hard-deletes. The record is removed permanently. The tool reads it first so the preview shows real current state and a bad id fails as validation — but it does not check whether bookings still reference it.
Confirmation tokens are single-use. A failed execution cannot be retried with the same preview; start a fresh save.
Cross-module links are ids only. Product sub-type references stay numeric; names resolve through product-types reads rather than cross-table joins here.
Field bounds are enforced at input. Dimensions outside 0–50000 mm or weight outside 0–100 tonnes fail validation before any write is staged.
Custom vehicles distinguish suggestion vs maximum. length_type selects whether stored dimensions act as suggestions or hard maxima alongside the min/max range fields.

Assets — physical fleet assets these option catalogues describe.
Settings — adjacent operator configuration surfaces within the same server.
BI — booking analytics that ultimately reflect choices made against these options.