Client types module — JetSetGo MCP reference

The clienttypes module manages the client-type taxonomy — the small set of classifications (such as Adult, Child, Agent, Senior) every client record carries and booking forms offer. Each type decides whether its clients may hold commission profiles, whether it appears on active booking forms, where it sits in display order, and which inventory allocation category it can draw on.

What the operator uses it for

Maintaining the classification list as the business changes: adding a category of customer, marking a type as agent-like so those clients can carry commission arrangements, retiring a type from booking forms without deleting it, fixing display order, or linking a type to an inventory allocation category. The set is deliberately small; most work is editing flags rather than adding rows.

Where it sits

Client types sit upstream of the clients CRM: every client references one, and the type's agent flag gates whether that client may carry a commission profile. The optional allocation-category link ties a type into capacity accounting. Booking forms read the active flag to decide what customers can pick.

Key concepts

Client type — a named classification applied to client records.
Agent flag — when true, clients of this type may carry a commission profile.
Active flag — controls visibility on booking forms; off means hidden but not deleted.
Sort order — display position; assigned automatically at the end of the list on create.
Allocation-category link — optional access to an inventory allocation category ("inventory citizen" in tool output).
Hard delete — deletion is permanent; there is no soft-delete state on this table.

Tools

Tool	Class	Purpose
`clienttypes_list`	Read	List all client types in sort order, with the allocation-category name resolved where the tenant's schema tracks it.
`clienttypes_get`	Read	One type by id, same name resolution.
`clienttypes_list_inventory_citizens`	Read	List allocation categories available for the link field, ordered by importance.
`clienttypes_save`	Guarded write	Create or update: name required on create; any subset updatable afterwards.
`clienttypes_reorder`	Guarded write	Bulk-update sort order across the set in one call.
`clienttypes_delete`	Guarded write (destructive)	Hard-delete a type; irreversible.

Rules worth knowing

Name is mandatory and capped (non-empty after trimming, at most 100 characters); descriptions cap at 500.
Sort order is automatic on create — new types join the end of the list. Set it explicitly only via update or clienttypes_reorder, which takes the full set of positions to apply.
Defaults on create: agent false, active true.
Deactivation is usually better than deletion. Deleting is a hard row removal with no undo; hiding a type from forms is done with the active flag instead.
The agent flag has downstream consequences. Toggling it changes whether existing and future clients of that type may carry commission profiles — the clients CRM clears profiles held by non-agent types automatically.
Name resolution degrades gracefully. Where a tenant's schema does not track the allocation-category relationship, reads fall back to bare ids rather than failing.

Clients — every client record carries one of these types; the CRM enforces the commission gate.
Commissions — owns the commission profiles only agent-flagged types may reference.