signupgenius_claim_slot
Sign up for a slot on a SignUpGenius sheet using your signed-in account. Preview the sheet, slot, and identity, then approve before the claim is submitted.
Instructions
Claim (sign up for) a slot on a slot-based SignUpGenius sheet. WRITES DATA the organizer sees, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call writes nothing and returns the preview (sheet, slot, identity) and a confirmToken, and only a repeat call with the same arguments plus that token submits — show the preview to the user and get their approval first (MCP_CONFIRM_MODE). Signs up as the signed-in account by default: omit firstname/lastname/email unless the user is signing up someone else (e.g. a family member). A supplied identity that differs from the account is allowed but flagged in the preview (identityDiffersFromAccount) — point it out to the user. For Yes/No/Maybe headcount sheets use signupgenius_rsvp instead.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"url": "<url>",
"slotitemid": "<slotitemid>"
},
"name": "signupgenius_claim_slot"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Sign-up URL or slug. | |
| No | Optional. Defaults to the signed-in account's email. | ||
| comment | No | Optional comment shown to the organizer. | |
| lastname | No | Optional. Defaults to the signed-in account's last name. | |
| quantity | No | Spots to take. Default 1. | |
| firstname | No | Optional. Defaults to the signed-in account's first name. Supply it only to sign up someone else (e.g. a family member); the preview then flags identityDiffersFromAccount. | |
| slotitemid | Yes | The slot to claim. Get this from signupgenius_list_slots. | |
| confirmToken | No | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation. | |
| customFields | No | Answers to the sheet's required custom questions. Read the required set from signupgenius_get_public_signup.customFields — omitting a required field makes the server reject the claim. |