Physical fleet assets module — JetSetGo MCP reference

The assets module manages an operator's physical fleet — the real vessels, buses, and other vehicles that deliver scheduled services. It is deliberately distinct from resources: a resource is a bookable product (what a customer purchases), while an asset is the physical vehicle assigned to actually run it. Each asset record carries a name, type, external identifier, icon, notes, an optional bound GPS tracker, and an active flag. Through JetSetGo MCP tools the assistant can list and inspect the fleet, create or edit assets, retire them, and issue or rotate a tracker's device key at the operator's request.

What the operator uses it for

Keeping the fleet roster accurate. Operators add newly acquired vehicles, correct identifiers or notes, attach or move GPS trackers as hardware changes, retire sold or withdrawn vehicles without destroying their history, and generate fresh device keys when a tracker needs re-pairing. In conversation, the assistant answers questions such as which vessels are currently active or whether a given bus has a tracker bound, straight from the same records.

Where it sits

Upstream, assets give physical substance to resources (a resource is a bookable product — an asset is what delivers its service) and to schedule, which assigns services to specific vehicles. Downstream, the tracker binding feeds live vehicle tracking by device id, and manifests reference which vehicle and crew actually ran a departure. The asset table is intentionally thin — identity, classification, tracker linkage, and lifecycle state — with operational detail living in the modules that consume it.

Key concepts

Asset — one physical vehicle: name (the only mandatory field), optional type, identifier, icon, notes, tracker binding, and active flag.
Asset type — fixed to vessel, bus, or other; new assets default to vessel.
Tracker binding — each asset may carry at most one GPS tracker id, and each tracker id may bind to at most one asset; database uniqueness enforces both directions.
Active vs retired — setting an asset inactive soft-retires it while preserving history; hard deletion removes the row permanently.
Device key rotation — issuing a new credential for an asset's GPS tracker; the plaintext is displayed exactly once at confirmation and never stored anywhere.
Guarded write — every mutation runs preview then confirm, fingerprinting the row so concurrent edits force a re-preview instead of applying stale intent.

Tools

Tool	Class	Purpose
`assets_list`	Read	List all fleet assets ordered by name.
`assets_get`	Read	Fetch one asset by id.
`assets_save`	Guarded write	Create an asset (name required) or update any subset of fields.
`assets_delete`	Guarded write	Hard-delete an asset permanently (destructive).
`assets_rotate_device_key`	Guarded write	Issue or rotate the GPS tracker device key; the new key is returned once.

Rules worth knowing

Prefer retiring via assets_save with the active flag off over deleting: deletion is a permanent hard delete, while retirement preserves the asset and everything referencing it.
Tracker bindings are unique in both directions — assigning a tracker already bound elsewhere fails with a database constraint violation rather than being silently re-pointed, and the tool does not pre-check for it.
Input is normalized on save: text fields are trimmed (empties become null), icons are lowercased, and system-managed fields such as ids and timestamps are never writable.
On creation only the name is mandatory; type defaults to vessel and the asset starts active.
Device-key rotation surfaces the new plaintext exactly once in the confirmation result; it is never stored server-side and never echoed into change records, so the operator must copy it immediately.
On some tenants the underlying table is not yet tracked in their metadata; reads then fail with a missing-field error, which is a provisioning gap rather than a tool fault.

Resources — the bookable products these assets physically deliver.
Schedule — assigns services onto specific fleet vehicles.
Tickets — passenger journeys ultimately fulfilled by an assigned asset.