add_day
ChatGPTAdd a date to the signup: date as YYYY-MM-DD in the signup's timezone. A date the signup already has comes back as that day with created: false and nothing seeded, so retrying is safe. On a repeating schedule a new date inside the schedule's range gets the schedule's Shifts (seededShifts); one outside it is created with none and unseededReason: "out-of-range" — tell the person, since extending the schedule will not fill it. Items every other date carries are copied onto a new date (seededItems). Notifies nobody. Returns { day, created, seededShifts, seededItems, unseededReason }; day.id is the day's id for the other day tools.
add_items
ChatGPTBulk-create items (things participants bring or contribute) on an existing signup. Each item has a name and quantityNeeded, plus optional description, maxPerPerson (the most units one person may claim; 0 or omitted = no limit), category, and askDetails. Each item may carry a scope: {kind:"day", dayId} to list it under one day (dayIds are in get_signup's days[]), {kind:"slot", slotId} to list it under one time slot (slotIds come from add_slots, get_signup_analytics slots[].id, or list_participants roster slot.id; get_signup returns no slots), or null/omitted for a whole-signup item that every participant sees. A day or slot of another signup is refused and nothing in the batch is written. A cancelled day or slot of this signup is accepted, but participants are not offered the item until it is uncancelled. Use right after create_signup to populate the items panel. Returns the inserted rows, each with its scope read back.
add_occurrence
ChatGPTAdd one extra Shift on one date of the signup's repeating schedule: seriesDate (YYYY-MM-DD, inside the schedule's range), start and end as HH:MM in the signup's timezone, and optionally label, capacity (default: the schedule's) and location. Use this, not add_slots, for a date that belongs to the schedule: the new date is edited on its own from then on, so later schedule edits leave it alone and the dates the schedule generates are unchanged. On a date the schedule already runs it becomes a second Shift at the next index. A date outside the range, or an end not after start, is refused and nothing is written. Notifies nobody. Returns { slot }, the new date, with seriesId and shiftIndex. Get seriesId from get_slot_coverage. location may be refused ("forbidden") for people outside a pre-GA rollout — tell the person, don't retry.
add_slots
ChatGPTBulk-create time slots on an existing signup. Each slot has start/end times, capacity, and optional title/description/location. Use right after create_signup to lay out a multi-slot event. Returns the inserted rows. Timezone contract (THE-206): supply timezone (IANA, e.g. America/Los_Angeles) and you can pass naive local ISO times (2026-09-15T17:00) — the server interprets them as wall-clock time in that zone. If you omit timezone we fall back to whatever zone is recorded on the parent signup; if neither is set, the existing UTC-only contract still applies (start/end must end in Z or carry an explicit offset). The slots themselves are always stored as UTC instants — the timezone only governs how the incoming strings are parsed.
cancel_day
ChatGPTCall one day of the signup off, IMMEDIATELY — there is no dry run, so confirm with the person first: dayId, optionally message (added to the email and text participants receive). Everyone holding anything on that day is emailed, and texted when they gave a phone number and SMS consent. Nothing is deleted: slots, items and signups are kept. A day with Shifts of a repeating schedule has each live Shift running that day cancelled: returns { kind: "series_date", cancelled, affectedParticipants, dayCancelledAt, notified } (affectedParticipants counts registrations). The whole day is called off, so a one-off slot on it is off too and its holder is told; dayCancelledAt is the instant this call called the day off (null when it was already off or nothing on it was live), and cancelled can be 0 while dayCancelledAt is set. It is undone with uncancel_day, which reconnects exactly the Shifts this call cancelled (or reconnect_occurrence for one Shift). Any other day (an ordinary signup's, or one with no schedule Shift) is itself cancelled: returns { kind: "day", day, affectedSignups, audience, confirmed, notified } (affectedSignups counts people), undone with uncancel_day. Cancelling again tells nobody twice. Find dayId in get_signup's days. Fails if the account behind this connection has not verified its email address.
cancel_occurrence
ChatGPTCancel one date (Occurrence) of the repeating schedule: slotId, optionally note (a private note for organizers, never shown to participants) and message (added to the email and text participants receive). The date and everyone registered on it are kept, and they are emailed that it is cancelled — notified says how many. Cancelling an already-cancelled date does nothing and notifies nobody. Undo it with reconnect_occurrence. A slot that is not part of a schedule is refused — remove it with the slot tools instead. Returns { slot, notified } with cancelledAt set. Find slotId in get_slot_coverage's per-date cells. Fails if the account behind this connection has not verified its email address.
cancel_signup
ChatGPTCancel the signup (status closed, signupCloseDate set to now) and EMAIL every attending registration that it is cancelled, immediately, with no undo. Ask the person you are acting for before you call it. message is PARTICIPANT-FACING: it is included in the cancellation email, and in the cancellation text for registrations with an account who have texts on, a phone and SMS consent. Omit it to send the standard notice with no note. Never put anything private in it. Returns the signup in get_signup's shape plus notified: recipients is the audience (attending registrations, including people who opted out of email); emails and sms are the notices actually sent. To close a signup WITHOUT telling anyone use set_signup_status with closed. A cancelled signup can be reopened with reopen_signup, which tells nobody that it is back on. Safe to retry: a repeat of a cancel that already told people returns the first call's notified and sends nothing. It tells people again only if the earlier close told nobody (set_signup_status closed, or no one was attending), if the signup was closed another way since, or if it was reopened in between. Requires the account behind this connection to have a verified email address. Wraps POST /v1/signups/{id}/cancel — reference: https://thesignup.app/v1/docs.
create_signup
ChatGPTCreate a draft signup — metadata only, no slots or items. Follow up with add_slots and/or add_items, then publish_signup to make it visible to participants. Returns the new id, slug, and draft status. Timezone contract (THE-206): supply timezone as an IANA name (e.g. America/Los_Angeles) and you can pass eventDate / signupCloseDate as naive local ISO strings (2026-09-15T17:00); the server interprets them as wall-clock time in that zone and stores the matching UTC instant + the zone for display. Omit timezone and the existing UTC-only contract still applies (eventDate must end in Z or carry an explicit offset).
create_slot_series
ChatGPTCreate the signup's repeating schedule (a Slot Series) and generate its dates in one step: one time slot per Shift per date the rule runs. Use it instead of add_slots when the same shifts repeat daily, weekly or monthly. Returns { series, slots }; read each Shift back with get_slot_coverage. rule is the shift plan: daily and monthly take genericShifts, weekly takes activeDays keyed by weekday number (0 = Sunday); each Shift is { start, end, label?, capacity?, question? } (question is an optional question asked of whoever signs up for that Shift) with HH:MM times in the signup's timezone. capacity is the default per date and a Shift's own capacity overrides it. A signup has at most one schedule, so a second call fails, and a range over 3660 days or more than 2000 Occurrences (dates times shifts) is refused with a message saying so — shorten the range or drop a shift. Repeating schedules need a paid plan: on a free plan the call fails with "Repeating slots require the pro tier; current tier is free." — tell the person, don't retry. Nothing is written on any failure, and generating dates notifies nobody.
delete_shift
ChatGPTDelete one Shift from the signup's repeating schedule and cancel its dates, IMMEDIATELY — there is no dry run and no second confirmation, so confirm with the person first. Name the Shift with shiftIndex (counting from 0; read it from get_slot_coverage) and, on a weekly schedule, weekday (0-6, 0 = Sunday; get_slot_coverage groups by shift without a weekday, so derive it from a date's startTime in the signup's timezone). Always pass expectStart and expectEnd (that Shift's current HH:MM start and end in the signup's timezone, from get_slot_coverage). Higher Shifts renumber down after a delete, so the same shiftIndex then names a different Shift — never retry without re-reading. If the Shift at that index has other times the call is refused as a conflict and nothing changes. Optionally note (a private note for organizers, never shown to participants) and message (added to the email and text participants receive). Every live date of that Shift is cancelled (kept, not deleted) and each participant registered on one is told it is cancelled by email, and by text when they gave a phone number and SMS consent; higher Shifts are renumbered down by one. Returns { confirmed, dates, affectedParticipants, notified }: dates cancelled, registrations on them, and who was told. A Shift the schedule does not have, or the schedule's last Shift (use delete_slot_series instead), is refused and nothing changes. Fails if the account behind this connection has not verified its email address.
delete_slot_series
ChatGPTDelete the signup's repeating schedule, IMMEDIATELY. Nothing participants see is destroyed: every date the schedule generated stays as an ordinary individual slot with its times, capacity and signups, and stops following the schedule (it can no longer be edited with the schedule tools, only with the slot tools). Cancelled dates stay cancelled. Notifies nobody. Returns { released, keptCancelled }: how many dates were released (cancelled ones included) and how many of those were cancelled. After this the signup has no schedule, so create_slot_series can make a new one. Get seriesId from get_slot_coverage.
extend_slot_series
ChatGPTMove the repeating schedule's end date out to newRangeEnd (YYYY-MM-DD) and generate the dates the rule produces in the new stretch; existing dates are untouched and nobody is notified. The range can only grow, a range over 3660 days or more than 2000 dates is refused with a message saying so. Returns { series, slots } — the dates just created. Extending creates new dates, so it needs a paid plan: on a free plan the call fails with "Repeating slots require the pro tier; current tier is free." — tell the person, don't retry. Nothing is written on any failure.
get_signup
ChatGPTFetch one signup by id, including title, slug, status, dates, location, and metadata. Returns an error if the id isn't visible to the calling org.
get_signup_analytics
ChatGPTLive participant/slot/item fill counts and the list of unfilled slots and items. Use this to answer 'how full is X?' or 'which slots still need volunteers?' Computed per call, not cached.
get_slot_coverage
ChatGPTFor a RECURRING signup, one entry per Shift — a repeating slot — rolled up across every date it runs: average fill, how many upcoming dates are staffed vs short (and which dates), unclaimed items, a cell per date, and the Regulars who usually take it. Use this to answer 'which Shift is chronically short?' or 'who normally covers Tuesday setup?'. Differs from get_signup_analytics, which is flat and event-wide and answers 'how full is this signup right now, and which individual slots and items still need people' — it has no notion of a Shift and cannot compare one date to another. Returns an empty list for a signup with no recurring slots; that is not an error. Regulars carry names and attendance counts and NO email addresses — reach someone via list_participants under its own scope.
list_participants
ChatGPTList every participant registered for the signup, with their slot/item bindings inlined. Returns an error if the signup isn't owned by the calling org.
list_signups
ChatGPTList recent signups owned by the calling org. Cursor-paginated (page size 1–100, default 20). There is no search endpoint — fetch and filter client-side, or use a known id with get_signup.
list_starred
ChatGPTList the signups the calling user has starred, upcoming only (past ones are omitted), soonest first. One entry per signup. going: true means the user also holds a spot on it: the entry then shows their earliest upcoming spot, and status and spotsLeft are null. going: false is a bookmark only: status is open, full or closed and spotsLeft is the places remaining (null means no limit). Starring never signs anyone up and organizers cannot see Stars. Use url to link the user to the signup, and register_self to sign them up.
message_participants
ChatGPTSENDS REAL EMAIL TO REAL PEOPLE. Every call delivers the subject and body you supply to the inboxes of everyone the Message Scope resolves to, immediately, with no undo and no dry-run. Ask the person you are acting for before you call it. Requires the messages:send scope, which exists only for this tool and this endpoint — holding reminders:send (fixed-body SMS to opted-in participants) or any read scope does NOT grant it. You choose WHO by naming a scope, not by naming people: all (everyone attending, no scopeId), day (everyone tied to one date, scopeId = that day's event_days id — read it off eventDayId/slot.eventDayId in list_participants), shift (one specific occurrence of a slot, scopeId = that time_slots id — read it off timeSlotId/slot.id in list_participants), person (one participant, scopeId = their registration id), roster (everyone who has ever held this repeating Shift, across every date it runs, scopeId = <seriesId>#<shiftIndex> — read seriesId/shiftIndex off get_slot_coverage), gaps (same people as roster, worded as an ask to cover a short date — same <seriesId>#<shiftIndex> scopeId). The server resolves the addresses; you cannot pass any, and an unrecognized field is rejected rather than ignored. Returns {recipients, sent, failed} — counts only, never addresses. One email per person however many commitments they hold. {name}, {slot} and {item} in the body are filled in per recipient. Metered per organization per UTC day in RECIPIENTS, not calls; a send that would cross the ceiling is refused whole and nothing goes out. Every call is written to the organization's audit log with your credential, the scope, the recipient count and the subject. Requires the account behind this connection to have a verified email address. To see who a scope covers BEFORE sending, read get_slot_coverage or list_participants under their own scopes. Wraps POST /v1/signups/{id}/messages — reference: https://thesignup.app/v1/docs.
move_commitment
ChatGPTMove one of a registration's slot commitments to another slot on the same signup, immediately. commitmentId is participant.id on that person's list_participants row (or commitments[].id on the registration); it keeps its id. toSlotId is a slot id from get_signup_analytics (slots[].id) or get_slot_coverage. The new slot's day is added to the days they attend. Refused, with nothing moved, when the target slot is full (the message gives its numbers) or on a past date, when the person already holds the target slot, when the commitment is an item rather than a slot, or when the commitment is on a past or cancelled date. Notifies nobody. registrationId is the registration's id: signup.id on a list_participants row (an Attend-only registration, one with no slot or item, has no list_participants row; GET /v1/signups/{id}/registrations lists it). A registration of another signup is not found. Moving to the slot it is already on changes nothing. Returns the registration. Wraps POST /v1/signups/{id}/registrations/{rid}/commitments/{commitmentId}/move.
move_occurrence
ChatGPTRe-time one date (Occurrence) of the repeating schedule: slotId, start and end as HH:MM in the signup's timezone (required even when unchanged), optionally date (YYYY-MM-DD) to move it to another day, location (only together with a move to another day), note (a private note for organizers, never shown to participants) and message (added to the email and text participants receive). Use this, not update_slot, for a date that belongs to a repeating schedule: the date keeps its place in the schedule (seriesDate, shiftIndex), is edited on its own from then on, and its signups and attendance move with it. Participants are emailed; notified says how many. A slot that is not part of a schedule is refused — use update_slot. Returns { slot, notified }. Find slotId in get_slot_coverage's per-date cells. Fails if the account behind this connection has not verified its email address. Sending date may be refused ("forbidden") for people outside a pre-GA rollout — tell the person, don't retry.
publish_signup
ChatGPTTransition a draft signup to published, opening it for registration. Idempotent — re-publishing is a no-op. Rejects (with a clear error) if the signup has been closed or canceled (a closed one is reopened with reopen_signup instead), or if the account behind this connection has not verified its email address.
register_participant
ChatGPTSign up someone OTHER than the caller. Takes their name + email plus at least one slot or item pick. For self-service flows (signing up the calling user), use register_self instead. Returns a receipt of what was confirmed and what failed — NOT the participant's manage link or confirmation token; the participant receives their manage link by email, and this tool does not return it. Successful registrations send a confirmation email, which cannot be undone. No SMS is sent: the confirmation text requires the participant's own consent, which this tool cannot grant on their behalf. Organizer signup notifications are suppressed for this tool.
register_self
ChatGPTSign UP the calling user (not someone else). Name and email come from their account — no participant input required. Use this for self-service flows; for registering someone else, use register_participant. Can register for an open signup outside the connected organization. Successful registrations send a confirmation email and may notify the organizer; these messages cannot be undone. No SMS is sent: the confirmation text requires consent given at a signup form, which this tool does not collect.
remove_item
ChatGPTDelete one item from the signup, IMMEDIATELY. Get itemId from get_signup's items. An item people have claimed is refused as a conflict and nothing changes — unless release_claims is true, which deletes the item AND every claim on it and emails (and texts, when they consented) the people who held an Open claim that it is gone. Confirm with the person first: claims cannot be restored. A claim on a past or cancelled date is history: it is deleted with the item and its holder is not emailed. message (only used with release_claims) is added to the top of that email and text and is read by participants — it is not a private note. Returns { id, deleted: true, claims, claimants, notified }: units that were claimed, people who held them, and who was emailed ({ recipients, emails, sms }); zeros for an unclaimed item. Deleting is by id, so a retry is a not-found error and emails nobody again. Fails if the account behind this connection has not verified its email address, because the call can email participants.
remove_participant
ChatGPTCancel a participant's registration. Destructive — removes the row immediately and fires a participant.canceled webhook. For participant-driven cancellation, prefer their confirmation-token link instead.
remove_registration
ChatGPTTake one person off the signup: every slot and item they hold and every day they attend is removed, immediately, and the registration is marked not attending. Notifies nobody. To remove only one of their slots or items use remove_participant. Refused, with nothing removed, while they hold a commitment on a past or cancelled date: that is history. registrationId is the registration's id: signup.id on a list_participants row (an Attend-only registration, one with no slot or item, has no list_participants row; GET /v1/signups/{id}/registrations lists it). A registration of another signup is not found. Safe to retry: a repeat returns the same end state. Returns the registration as it now stands. Wraps DELETE /v1/signups/{id}/registrations/{rid}.
remove_slot
ChatGPTDelete one empty one-off time slot from the signup, IMMEDIATELY. Get slotId from get_signup's slots (or get_slot_coverage). Refused, with nothing deleted: a slot that has registrations (also on a past date; remove the registrations first), a slot with an item scoped to it that has claims (remove_item with release_claims, or re-scope the item, first), and a date of a repeating schedule — one whose seriesId is set. To drop just one date of a schedule use cancel_occurrence instead. Items scoped to the slot that nobody has claimed are NOT deleted: they become whole-signup items (scope: null) available on every date. Notifies nobody. Returns { id, deleted: true }. Deleting is by id, so it is safe to retry: a second call for the same slot is a not-found error and changes nothing.
reopen_signup
ChatGPTSet the signup's signupCloseDate and, if the signup is closed, make it published again — the only way to reopen one (update_signup and set_signup_status cannot). signupCloseDate must be in the future: a past or present date is refused and nothing is written. ISO-8601: UTC / offset-bearing, or a naive local string (2026-09-15T17:00) read in the signup's own timezone. On a signup that is already published it only replaces signupCloseDate (earlier or later); on a draft it sets the date and the status stays draft. Registrations, slots and items are untouched. Notifies no participants and emits one signup.updated webhook, so a reopened signup is not announced to participants: use message_participants if people should know. Like publish_signup, it needs the account behind this connection to have a verified email address. Returns the signup in get_signup's shape, days included. WARNING: it also revives a signup that was CANCELLED (cancelling closes it), including one whose participants were told it is cancelled; the reopen sends them nothing, so message them if that matters. Calling it again with the same date leaves the same end state, so it is safe to retry.
resend_confirmation
ChatGPTEMAIL the person their signup confirmation again, now, at the registration's address: what they hold, the days they attend, and their manage link. One email per call; it cannot be unsent, so do not call it twice for one request. Each counts against the organization's daily message-recipient ceiling. Works for an Attend-only registration; refused for a registration that is no longer attending. registrationId is the registration's id: signup.id on a list_participants row (an Attend-only registration, one with no slot or item, has no list_participants row; GET /v1/signups/{id}/registrations lists it). A registration of another signup is not found. Requires the account behind this connection to have a verified email address. Returns { sent: true }. Wraps POST /v1/signups/{id}/registrations/{rid}/resend_confirmation.
send_reminder
ChatGPTSend SMS reminders to opted-in participants who haven't already received one for this signup. Returns counts (eligible/sent/failed). Subject to the org's SMS ceiling. Requires the account behind this connection to have a verified email address.
set_occurrence_capacity
ChatGPTSet how many spots one date (Occurrence) of a repeating schedule has (capacity, a whole number of at least 1). Only that date's number changes; the date keeps following the schedule, so a later change to every date still reaches it. Its time and place stay as they are. A number below the spots already taken is refused and nothing is written. Notifies nobody. Returns { slot }. Find slotId in get_slot_coverage's per-date cells.
set_occurrence_max_per_person
ChatGPTSet how many spots one person may take on one date (Occurrence) of a repeating schedule (maxPerPerson; 1 = one spot per person). Only that date's number changes; the date keeps following the schedule, so a later change to every date still reaches it. Its time and place stay as they are. A number above this date's spots — or above the series ceiling when this date's spots are uncapped — is refused and nothing is written. A cap below what someone already holds is kept — it limits further signups and removes nobody. Notifies nobody. Returns { slot }. Find slotId in get_slot_coverage's per-date cells.
set_signup_status
ChatGPTTransition a signup to any valid status. Use to unpublish (published -> draft), close a signup early (-> closed), or revert a mistaken publish (-> draft). Idempotent — setting the current status is a no-op. A closed signup can't be moved to another status here (mirrors the publish_signup rule): reopen it with reopen_signup, which also sets a new close date. Moving to published requires the account behind this connection to have a verified email address (same as publish_signup); draft and closed do not. Unpublishing keeps every existing registration: those people hold their spots and can still cancel, but cannot open the page until it is republished — the response carries a warning with the count when anyone is affected.
set_slot_series_max_per_person
ChatGPTSet how many dates of the repeating schedule one person may take (maxPerPerson; 0 = no limit), on the schedule and on every date that has not been edited on its own. A cap below what someone already holds is kept — it limits further signups and removes nobody. Notifies nobody. Returns the updated series.
star_signup
ChatGPTBookmark a signup for the calling user so it shows in list_starred and on their Agenda. Starring NEVER signs the user up and holds no spot; use register_self for that. A Star is private to the user: organizers cannot see who has starred their signup. Idempotent. Works on any published signup, including one outside the connected organization; a draft, closed or unknown signup is reported as not found, so a closed signup cannot be starred again. Takes signupId, the signup's id.
uncancel_day
ChatGPTPut a cancelled day back (one cancel_day answered with kind: "day"): dayId. Its slots, items and signups are live again. Notifies nobody. A day that is not cancelled comes back unchanged. A day with Shifts of a repeating schedule gets back the Shifts the same cancel took down (cancel_day answered kind: "series_date"): restored counts them, and notRestored lists { slotId, reason } for any that could not come back (their Shift left the schedule, or their place is taken), which stay cancelled; use reconnect_occurrence once that is fixed. A Shift cancelled earlier on its own stays cancelled and is not listed. A day whose Shifts were all cancelled one by one, with no day cancellation, is refused — use reconnect_occurrence on each Shift (slot ids in get_slot_coverage). Returns { day, restored, notRestored }. Find dayId in get_signup's days.
update_item
ChatGPTEdit one item of the signup: supply only the fields to change (name, description, quantityNeeded, maxPerPerson, category, sortOrder, customField, askDetails). scope moves the item: {kind:"day", dayId} lists it under one day (dayIds are in get_signup's days[]), {kind:"slot", slotId} under one time slot, null makes it a whole-signup item; leave scope out to keep it where it is. A day or slot of another signup is refused and nothing changes. Get itemId from get_signup's items. Returns the updated item with its scope read back. An empty edit returns the item unchanged. Setting the same values again changes nothing, so it is safe to retry.
update_registration
ChatGPTEdit one person's registration on a signup, immediately: supply only the fields to change (name, email, phone, attendees, nameVisible, days); at least one is required. email is written directly (no confirmation email to either address); another registration on this signup already using it is refused. phone null clears it, and a different number turns the person's SMS consent off. attendees counts the person plus anyone they bring, at most the signup's maxAttendeesPerSignup. nameVisible is whether their name shows on the public signup page. days is the COMPLETE list of event day ids they attend (ids are days[].id on get_signup), and a day you omit is REMOVED. Read the current set first: list_participants rows for this person with eventDayId set and timeSlotId and itemId both null, or the days returned by an earlier call of this tool. Removing attendance is allowed on any day, and [] removes all of it while their slots and items stay; repeating the same list changes nothing. Adding a day follows the Guest's rules: the signup must be accepting signups, a cancelled date is refused, a required day question must already be answered, and on a signup that requires a commitment no day can be added (attendance removed there cannot be re-added with days). Also refused: adding a day that has passed, and adding any day while the registration is no longer attending ([] still works). A day of another signup is not found. Any refusal changes nothing. Notifies nobody. registrationId is the registration's id: signup.id on a list_participants row (an Attend-only registration, one with no slot or item, has no list_participants row; GET /v1/signups/{id}/registrations lists it). A registration of another signup is not found. Returns the registration with its commitments. Wraps PATCH /v1/signups/{id}/registrations/{rid}.
whoami
ChatGPTIdentify which organizations this connection can act in and which scopes were granted. Call first to confirm context before doing real work. organization is the default org — the one used when a tool is called without organization_id. organizations lists every org reachable from this connection, each with the scopes in force there; pass one of their ids as organization_id on any tool to act in it. Also returns a quotas map keyed by scope (ai:draft, messages:send) with used, limit, remaining, and period. Unlimited quotas (Pro+) report limit: null and remaining: null. messages:send is never unlimited — it counts RECIPIENTS emailed today (UTC), so read remaining before calling message_participants on a large scope.
add_items
Claudeadd_slots
Claudecreate_signup
Claudeget_signup
Claudeget_signup_analytics
Claudeget_slot_coverage
Claudelist_participants
Claudelist_signups
Claudemessage_participants
Claudepublish_signup
Clauderegister_participant
Clauderegister_self
Clauderemove_participant
Claudesend_reminder
Claudeset_signup_status
Claudewhoami
Claude