Skip to main content
Glama
chrischall

signupgenius-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

signupgenius_claim_slot

Claim a slot on a slot-based SignUpGenius signup sheet. Use a dry run to preview the slot and identity, then confirm with true to submit only after explicit user approval.

Instructions

Claim (sign up for) a slot on a slot-based SignUpGenius sheet. Two-step by design: call WITHOUT confirm first to get a preview of the slot, identity and payload, show it to the user, then call again with confirm:true. WRITES DATA — never call with confirm:true unless the user has explicitly approved this specific slot. For Yes/No/Maybe headcount sheets use signupgenius_rsvp instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesSign-up URL or slug.
emailYes
commentNoOptional comment shown to the organizer.
confirmNoMust 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.
lastnameYes
quantityNoSpots to take. Default 1.
firstnameYes
slotitemidYesThe slot to claim. Get this from signupgenius_list_slots.
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. 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,}$"
  2. Addedv1.6.0

TDQS

A4.7/5.0
Behavior5/5

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

It goes beyond readOnlyHint/destructiveHint by explicitly stating 'WRITES DATA' and describes the dry-run behavior when confirm is omitted. It also defines the approval gate before mutating data, which annotations cannot convey. This is strong behavioral disclosure.

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

Conciseness5/5

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

The description is compact, front-loaded with the core purpose, and every sentence earns its place: purpose, two-step behavior, safety warning, and sibling routing. No filler or repetition.

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 write operation with no output schema, it covers the key contexts an agent needs: preview-then-confirm, write-active, explicit user approval, and which sibling to use for other sheet types. It is complete enough to call and show a user a preview confidently.

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

Parameters3/5

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

The description adds operational meaning to confirm (preview vs submit), but most parameter meaning is already in the schema, with about 67% coverage. Fields like firstname, lastname, and url are self-explanatory, and slotitemid/customFields are documented in the schema. The description contributes workflow context rather than new parameter-level detail.

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?

The description opens with a specific verb and resource: 'Claim (sign up for) a slot on a slot-based SignUpGenius sheet.' It also distinguishes this tool from the headcount-focused sibling signupgenius_rsvp, and references how slot IDs are obtained via signupgenius_list_slots in the schema. An agent can tell exactly what this tool does without opening the 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?

The description gives an explicit two-step workflow: call without confirm to preview, show the user, then call again with confirm:true. It also warns not to set confirm:true without explicit user approval and tells the agent to use signupgenius_rsvp instead for Yes/No/Maybe sheets. This is clear, actionable guidance with exclusions.

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

Deploy Server

Other Tools