265f39663518_submit_ticket_request
ChatGPTWrite the ticket request to nexus after the user has confirmed. Re-parses the submitted form data + carried context into a validated TicketRequestCreate (this construction is the input-validation boundary), then serializes it to the guest payload. This is the real gate: backend tools are hidden from the model's tools/list, but that is a host-layer guarantee — FastMCP does not enforce caller-origin, so this re-validation plus nexus's own authorization are the enforced boundaries. Returns a success message; raises ToolError when not confirmed, on validation failure, or on a nexus error.
a52073893183_review_ticket_request
ChatGPTValidate submitted form data and return a Markdown summary for the confirmation page. Reconstructs the event context from the carried `context` dict (no nexus calls). Returns the summary on success; raises ToolError on validation failure (surfaced via the CallTool on_error).
b71a439f5027_load_event_context
ChatGPTGather one event's ticketing context for the in-form event picker. Called from the app when the user selects an event in the Combobox. Wraps gather_event_context and returns the serialized EventContext (tiers/pass types/departments, each qty defaulting to 0) for SetState("ctx", RESULT) on the client.
create_ticket_request
ChatGPTOpen an interactive app to request tickets and passes for an event. The form always renders a searchable event Combobox; selecting an event calls load_event_context (which writes the event's tiers/passes/departments into state), and the tier/pass/department fields render reactively from that state. When event_id is provided it is pre-selected and its context pre-seeded. Any provided guest name/email/affiliation prepopulate the corresponding form fields (seeded into the initial state). Submitting calls review_ticket_request then, on approval, submit_ticket_request (the write).
get_info
ChatGPTReport the running Artist Growth MCP server's build version, environment, and provenance.
list_artists
ChatGPTList the artists the caller has permission to access, each with its pk and name. Reach for this only when the user wants to focus on one specific artist: call it to resolve that artist's pk (filter by name), then pass the pk to narrow another tool (search_events, list_calendars, list_my_tasks, search_ticket_requests). It is not a required first step — those tools already span every artist you can access when no pk is given. Also use it to answer "which artists can I access?". Page with an opaque cursor.
list_calendars
ChatGPTList the calendars you can access, each with a consolidated view of everything scheduled in a window. Each calendar groups all of its scheduled items for the window: events, calendar items (load-in, soundcheck, and other day-of logistics), transportation (flights, ground), and accommodations. This is the whole-schedule overview across one or more artists — to search or filter events specifically (by text, type, or status), use search_events instead. A date_from/date_to window is required and may span at most one year. Optionally narrow to one or more artists with artist_ids, and page through calendars with cursor.
list_my_tasks
ChatGPTList your tasks — the dedicated way to answer "what's mine", "what's overdue", or "what's due". Scoped to you (the signed-in caller) via your bearer token; Artist Growth enforces what you can see. By default it returns every task you can see; pass role to narrow to one relationship you hold — assignee (assigned to you), creator (you created it), or assigner (you assigned it to someone). role and every other filter only narrow the tasks you can already see — they never widen access. Narrow further by organization, project, event, due-date window (due_before/due_after), or priority; by default only incomplete tasks are returned (set include_completed to include done ones). Each task carries a derived due_status (OVERDUE / DUE_TODAY / UPCOMING / NO_DUE_DATE / COMPLETED). Page through results with cursor.
search_events
ChatGPTSearch Artist Growth events the caller has permission to see. Use this to find specific events by free text, date range, artist, status, and/or event type. For a whole-schedule overview that also includes calendar items, transportation, and accommodations across one or more artists, use list_calendars instead. Results are permission-scoped to the authenticated user and page with an opaque cursor.
search_ticket_requests
ChatGPTSearch ticket requests the caller has permission to see. Each result is one ticket request — the requesting guest, who submitted it, who approved it, the department, requested ticket tiers and passes, and the event it is for. Results are permission-scoped: the caller sees only the ticket requests they are authorized to view (no cross-organization leakage). Filter by event, artist, department, event group, status, the event-date window, and the submission-date window; use cursor to page.
create_ticket_request
Claudeget_info
Claudelist_artists
Claudelist_calendars
Claudelist_my_tasks
Claudesearch_events
Claudesearch_ticket_requests
Claude
