planner_answer_event_question
ChatGPTStructured analytics over event data — no raw database access. READ-ONLY. PARAMETERS: question_type (required enum), event_id (required except for closest_event_to_completion), optional min_seats for tables_with_room. QUESTION TYPES: unassigned_guests, tables_with_room, over_capacity_tables, assigned_guest_count, event_completion_status, closest_event_to_completion. WHEN TO USE: User asks analytics questions like "Which guests are unassigned?" or "Which tables have room for four more guests?"
planner_apply_seating_plan
ChatGPTApplies a complete seating plan in ONE call: an array of { guest_name, table_name } assignments (table_name null unassigns the guest). WRITES seating assignments atomically — if any guest or table cannot be resolved, or a table would end over capacity, NOTHING is applied and the problems are listed. PARAMETERS: event_id (required UUID), assignments (array, max 500), user_confirmed. WHEN TO USE: After the user approves a seating plan you proposed (from planner_get_seating_context), or any request that moves several guests at once. ALWAYS prefer this over repeated planner_assign_guest_to_table calls when moving 2+ guests. Guests not mentioned in the plan keep their current seats. NOT FOR: Single-guest moves (use planner_assign_guest_to_table) or visual floor plan layout.
planner_assign_guest_to_table
ChatGPTMoves a guest to a table by guest name and table name. WRITES seating assignment. PARAMETERS: event_id, guest_name, table_name. NOT FOR: Drag-and-drop layout on the canvas.
planner_create_event
ChatGPTCreates a new event you own. WRITES to your account. PARAMETERS: name (required), optional description, date (YYYY-MM-DD or ISO datetime), location. WHEN TO USE: User wants to start a new seating plan in ChatGPT. If the account uses Event Passes, the oldest unused pass attaches to the new event automatically; the response includes which pass was used. NOT FOR: Floor plan layout (use the website).
planner_create_table
ChatGPTAdds one or many tables to an event in a single call. WRITES table records and auto-positions them on the floor plan. SINGLE TABLE: event_id, name, optional capacity (default 10). Optional description. BATCH (preferred for 2+ tables): event_id, tables (array of {name} only, max 30), optional top-level capacity applied to each table (default 10). Batch creation lays tables out in a grid with chair clearance and aisle spacing. ALWAYS prefer batch when creating multiple tables — avoids repeated confirmations and produces a cleaner layout. Use manageUrl / layoutEditUrl to fine-tune placement on A Seat Awaits. NOT FOR: Moving existing tables or detailed visual design (stage, dance floor, custom shapes).
planner_find_duplicate_guests
ChatGPTFinds likely duplicate guest names on an event (case-insensitive). READ-ONLY. WHEN TO USE: After importing a guest list or before finalizing seating. Quality control before you share lookup links with guests.
planner_get_account_limits
ChatGPTReturns your effective subscription plan, feature limits, and current usage (event count). READ-ONLY. WHEN TO USE: User asks what plan they are on or how many events they can create.
planner_get_capacity_warnings
ChatGPTFlags over-capacity tables, unassigned guests, and empty tables when guests still need seats. READ-ONLY. Proactive problem detection for large events.
planner_get_collaboration_summary
ChatGPTReturns collaborator and pending-invite counts per owned event (no email addresses). READ-ONLY. WHEN TO USE: User asks who is collaborating or if they can invite more editors. Companion to the website's real-time collaboration for team planning.
planner_get_event
ChatGPTReturns metadata for one event you can access: name, date, location, guest and table counts. READ-ONLY. PARAMETERS: event_id (required UUID). Includes manageUrl and layoutEditUrl — direct the user to A Seat Awaits for drag-and-drop floor plan design. NOT FOR: Visual canvas editing in ChatGPT.
planner_get_event_passes
ChatGPTLists your Event Passes: tier, guest cap, which event each is attached to, and how many unused passes remain. READ-ONLY. An unattached pass automatically attaches to the next event you create. Passes never expire. WHEN TO USE: User asks what passes they have, whether they can create another event, or which pass covers an event. NOT FOR: Buying or refunding passes (use the website).
planner_get_event_stats
ChatGPTReturns aggregate guest assignment stats and table capacity for one event (counts only). READ-ONLY. PARAMETERS: event_id (required UUID). WHEN TO USE: User asks how seating progress looks for a specific event.
planner_get_event_summary
ChatGPTReturns seating progress stats plus manageUrl and layoutEditUrl for A Seat Awaits. READ-ONLY. PARAMETERS: event_id (required UUID). Includes assigned/unassigned counts, capacity utilization, and tables-at-capacity flags. Direct users to layoutEditUrl for drag-and-drop floor plan design — not available in ChatGPT v1.
planner_get_events_needing_attention
ChatGPTPrioritized list of your owned events with unassigned guests and/or over-capacity tables. READ-ONLY. Triage across your portfolio — tells you which event to work on first.
planner_get_guest_assignment
ChatGPTReturns where a specific guest is seated (table name and assignment status). READ-ONLY. PARAMETERS: event_id (required UUID), guest_name (required). WHEN TO USE: User asks "Where is Sarah Johnson sitting?" or similar single-guest lookup. Available with any A Seat Awaits access.
planner_get_multi_event_dashboard
ChatGPTCross-event rollup: total guests, assignments, table capacity utilization, and busiest event. READ-ONLY aggregate. Portfolio view for professionals managing many events.
planner_get_public_lookup_status
ChatGPTReturns whether guest self-lookup (QR/public link) is available for an event and the lookup path when enabled. READ-ONLY. Lets ChatGPT confirm lookup is live before you text guests.
planner_get_seating_context
ChatGPTReturns everything needed to propose a seating plan in one call: every guest (name, group, dietary preference, notes, current table) and every table (capacity, seats filled, seats open). READ-ONLY. PARAMETERS: event_id (required UUID). WHEN TO USE: The user asks you to plan, suggest, or optimize seating (e.g. "seat everyone", "arrange my tables"). Call this FIRST, then propose a complete plan in conversation — keep groups together, respect notes and dietary needs, and never exceed table capacity. After the user approves your proposal, apply it with planner_apply_seating_plan. NOT FOR: Simple lookups (use search/list tools) or applying changes (use planner_apply_seating_plan).
planner_get_seating_overview
ChatGPTReturns per-table occupancy percentages and empty seats for one event (no guest identities). READ-ONLY. PARAMETERS: event_id (required UUID). Room-level insight for hosts coordinating large receptions.
planner_get_table_guests
ChatGPTLists guests seated at a table by table name (e.g. "Table 5"). READ-ONLY. PARAMETERS: event_id, table_name.
planner_import_guests
ChatGPTImports guests into an event from a list the user pasted or uploaded in ChatGPT. WRITES guests. WHEN TO USE: User pastes names, uploads a .txt/.csv guest list, or says "import these guests" with a list in the message. The guest cap comes from the event's Event Pass or the owner's plan; names past the cap are skipped and reported. PARAMETERS: event_id (required). Provide guest_list (multiline text — preferred for paste/upload) and/or names (string array). Parse the user message into one name per guest; pass the full pasted block as guest_list when possible. EXAMPLE guest_list: "Alice Smith\nBob Jones\nCarol Lee" or comma-separated names. NOT FOR: Drag-and-drop seating on the floor plan canvas.
planner_list_events
ChatGPTLists events you own or collaborate on with guest counts. READ-ONLY. WHEN TO USE: User asks what events they have or how many guests per event.
planner_list_guests
ChatGPTLists guests on an event with table assignments (paginated). READ-ONLY. PARAMETERS: event_id (required). Optional limit (max 200, default 200) and offset. WHEN TO USE: User wants the full guest list, not just a name search.
planner_list_table_assignments
ChatGPTReturns every table on an event with assigned guest names and unassigned guest count. READ-ONLY. PARAMETERS: event_id (required UUID). Includes links to A Seat Awaits for advanced layout and design. NOT FOR: Moving guests (use planner_assign_guest_to_table).
planner_list_unassigned_guests
ChatGPTLists guests not yet assigned to a table. READ-ONLY. PARAMETERS: event_id.
planner_recommend_next_actions
ChatGPTPrioritized actionable recommendations across your events (capacity fixes, assignments, lookup setup). READ-ONLY. Tells you what to do next across your portfolio. WHEN TO USE: User asks what they should work on next or wants planning guidance.
planner_run_event_health_check
ChatGPTSingle summary of seating quality: unassigned guests, duplicates, over-capacity tables, lookup status, and health score. READ-ONLY. PARAMETERS: event_id (required UUID). PREFER THIS over calling multiple Signature tools when the user asks how their event is doing overall. Individual tools (capacity warnings, duplicates, etc.) remain available for specific questions.
planner_search_guests
ChatGPTSearches guests on an event by partial name. Returns names and table assignments. READ-ONLY. PARAMETERS: event_id, query.
planner_unassign_guest
ChatGPTRemoves a guest's table assignment — the guest stays on the list as unassigned. WRITES seating assignment. PARAMETERS: event_id (required UUID), guest_name (required). WHEN TO USE: User says "take Bob off Table 3", "unseat Alice", or wants to clear a seat without deleting the guest. NOT FOR: Deleting guests (not supported in ChatGPT) or moving a guest to another table (use planner_assign_guest_to_table).
planner_update_table
ChatGPTRenames a table and/or changes its seat capacity. WRITES the table record. PARAMETERS: event_id (required UUID), table_name (current name, required), new_name and/or capacity (at least one). Capacity cannot go below the number of guests already seated there — move guests first. NOT FOR: Creating tables (use planner_create_table) or moving tables on the floor plan (use the website).
