Local events and holidays module — JetSetGo MCP reference

The localevents module maintains two small reference datasets that shape operational planning: local events (concerts, sports fixtures, festivals, conferences and similar) that affect transport operations in an operator's area, and public holidays. Each event carries a name, description, start and end datetimes, optional location, an impact level of low, medium, or high, and one of eight event types. Holidays are simple date-plus-name records. Through JetSetGo MCP tools the assistant can read both datasets for planning conversations and create, update, or remove records at the operator's request.

What the operator uses it for

Recording foreseeable demand pressure before it arrives. A major festival weekend, a stadium concert, or a cruise-ship conference changes passenger volumes and road conditions; logging these with an impact level gives scheduling discussions shared context. The holiday list is the other half: dates when normal demand patterns shift or services run differently. Operators typically maintain this data ahead of season and let the assistant consult it when discussing availability, staffing, or capacity with them.

Where it sits

This is upstream reference data feeding downstream planning. It does not itself block bookings or alter schedules — nothing here hard-constrains another module. Instead, schedule and availability conversations consume it as context: when an assistant reason about a date range, it can check for overlapping high-impact events and holidays and factor them into recommendations. It pairs naturally with schedule (which assigns services to time slots) and with the seasonal patterns an operator describes in their knowledge content.

Key concepts

Local event — a dated occurrence affecting operations: name, optional description and location, start/end datetimes, impact level, and event type.
Impact level — low, medium, or high; the operator's judgement of how much the event disrupts normal operations.
Event type — one of eight fixed values: concert, sports, festival, conference, holiday, market, exhibition, other.
Public holiday — a bare date-and-name record, ordered by date in listings.
Save semantics — one tool handles both create and update per entity type; omitting the id creates, providing it updates any subset of fields.
Soft vs hard delete — events are soft-deleted (marked deleted, recoverable in principle); holiday deletion is permanent.

Tools

Tool	Class	Purpose
`localevents_list`	Read	List non-deleted local events, newest start first.
`localevents_get`	Read	Fetch one local event by id.
`localevents_holidays_list`	Read	List public holidays ordered by date.
`localevents_holidays_get`	Read	Fetch one public holiday by id.
`localevents_save`	Guarded write	Create or update a local event (preview then confirm).
`localevents_delete`	Guarded write	Soft-delete a local event (destructive).
`localevents_holidays_save`	Guarded write	Create or update a public holiday (preview then confirm).
`localevents_holidays_delete`	Guarded write	Hard-delete a public holiday (destructive).

Rules worth knowing

Creating an event requires name plus both start and end datetimes; creating a holiday requires name plus a calendar date. Updates are partial — supply only what changes.
The two entity types behave differently on delete: events are soft-deleted via a flag while holidays are removed permanently by id. Both deletions are previewed and require confirmation.
Impact level and event type are constrained to their fixed enumerations; anything else fails validation cleanly rather than being coerced.
Event listings exclude deleted rows and order by start datetime descending; holiday listings order by date ascending.
Change records distinguish the entity types explicitly (local_event versus holiday), so audit history stays unambiguous even though both live in one module.
All writes are guarded: every mutation returns a preview of the exact change first and executes only after explicit confirmation, with fingerprint checks so concurrent edits trip a re-preview instead of applying stale intent.

Schedule — consumes event and holiday context when assigning services to time slots.
Settings — tenant-level configuration alongside which this reference data is maintained.
Resources — bookable products whose availability planning references local conditions.