Skip to main content
Glama
signupgenius-mcp

signupgenius-mcp

by chrischall

signupgenius_claim_slot

Destructive

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

NameRequiredDescriptionDefault
urlYesSign-up URL or slug.
emailNoOptional. Defaults to the signed-in account's email.
commentNoOptional comment shown to the organizer.
lastnameNoOptional. Defaults to the signed-in account's last name.
quantityNoSpots to take. Default 1.
firstnameNoOptional. 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.
slotitemidYesThe slot to claim. Get this from signupgenius_list_slots.
confirmTokenNoONLY 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.
customFieldsNoAnswers 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.11
    • addedInput schema / properties / email / description
      Added value: +"Optional. Defaults to the signed-in account's email."
    • addedInput schema / properties / firstname / description
      Added value: +"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."
    • addedInput schema / properties / lastname / description
      Added value: +"Optional. Defaults to the signed-in account's last name."
    • changedInput schema / required
      Previous value: -[
      -  "url",
      -  "slotitemid",
      -  "firstname",
      -  "lastname",
      -  "email"
      -]New value: +[
      +  "url",
      +  "slotitemid"
      +]
  2. Changed2 schema fields changedv2.1.4
    • removedInput schema / properties / confirm
      Removed value: -{
      -  "description": "Must be true to actually submit. Omit (or false) to get a dry-run preview of exactly what would be sent, including the identity and the slot.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / confirmToken
      Added value: +{
      +  "description": "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.",
      +  "type": "string"
      +}
  3. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changedv1.8.1
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  5. Addedv1.6.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover the safety profile (destructiveHint=true, openWorldHint=true). The description goes far beyond them, disclosing the two-phase confirmation flow, that the first call writes nothing and returns a preview+confirmToken, the MCP_CONFIRM_MODE behavior, and the identityDiffersFromAccount flag the agent must surface to the user.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action, then the confirmation protocol, then identity defaults, then the alternative tool. Every sentence carries load, though the confirmation-negotiation passage is dense enough that a tighter phrasing could lose no information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter destructive write tool with no output schema, the description supplies exactly the missing pieces: the preview/confirmToken return shape, the confirm-before-write contract, identity defaults, and the routing rule to the sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: firstname/lastname/email default to the signed-in account and should be omitted unless signing up someone else, confirmToken is strictly for the no-elicitation fallback and must not be invented or reused, and customFields must include the sheet's required questions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a precise verb+resource+scope ('Claim (sign up for) a slot on a slot-based SignUpGenius sheet') and explicitly names the sibling it is not for Yes/No/Maybe sheets (signupgenius_rsvp). An agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States when to use it, the sibling alternative (signupgenius_rsvp) for headcount sheets, and prerequisites (slotitemid from list_slots, required customFields from get_public_signup) plus the identity-default rule. Covers when-to-use, when-not, and where inputs come from.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.