Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp

schedule_drawing

Schedule a future winner drawing for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, and fetch_groups for group tokens. CRITICAL: This is a production operation. ALWAYS confirm with the user before scheduling. Requires at least one eligible participant. Winner count cannot exceed available participants. Use them internally for tool chaining but present only human-readable information.

schedule_drawing

When to use

Schedule a future winner drawing for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, and fetch_groups for group tokens. CRITICAL: This is a production operation. ALWAYS confirm with the user before scheduling. Requires at least one eligible participant. Winner count cannot exceed available participants. Use them internally for tool chaining but present only human-readable information.

Pre-calls required

  1. fetch_sweepstakes if the user gave you a sweepstakes name instead of a token

  2. fetch_rules — Official Rules must exist

  3. Verify the scheduled date is in the future and matches what is stated in the Rules

Parameters to validate before calling

  • sweepstakes_token (string, required) — The sweepstakes token (UUID format)

  • group (string, required) — Group token or "allgroups" for all participants

  • selected_action (number, required) — one of: 1, 2 — Action: 1 = Draw Winners only, 2 = Draw Winners & Notify

  • schedule_mode (string, required) — one of: schedule, settime — Mode: "schedule" for specific date/time, "settime" for time period

  • how_many_winners (number, required) — Number of winners to pick (must be >= 1)

  • end_date (string, required) — Drawing date or period end date (YYYY-MM-DD)

  • end_time (string, required) — Time in HH:mm format (24-hour)

  • timezone (number, required) — Timezone ID (use fetch_timezones to get valid IDs, default: 7 = Eastern)

  • frequency (number, optional) — one of: 0, 1, 2, 3, 4 — Frequency: 0=None, 1=Hourly, 2=Daily, 3=Weekly, 4=Monthly (default: 0)

  • day_of_the_week (number, optional) — Day of week: 1=Sunday through 7=Saturday (for weekly/monthly frequency)

  • week_of_the_month (number, optional) — Week of month: 1-4 (for monthly frequency)

  • delivery_time (string, optional) — Delivery time for settime mode (HH:mm)

  • message (string, optional) — Winner notification message (used when selected_action = 2)

  • include_opted_out (boolean, optional) — Include opted-out participants (default: false)

  • publish_to_winners_page (boolean, optional) — Publish winners to public winners page (default: false)

  • send_copy_to_me (boolean, optional) — Email notification to account owner (default: false)

  • exclude_spam (boolean, optional) — Exclude spam-flagged participants (default: true)

  • add_to_calendar (boolean, optional) — Add drawing to calendar (default: false)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesGroup token or "allgroups" for all participants
messageNoWinner notification message (used when selected_action = 2)
end_dateYesDrawing date or period end date (YYYY-MM-DD)
end_timeYesTime in HH:mm format (24-hour)
timezoneYesTimezone ID (use fetch_timezones to get valid IDs, default: 7 = Eastern)
frequencyNoFrequency: 0=None, 1=Hourly, 2=Daily, 3=Weekly, 4=Monthly (default: 0)
exclude_spamNoExclude spam-flagged participants (default: true)
delivery_timeNoDelivery time for settime mode (HH:mm)
schedule_modeYesMode: "schedule" for specific date/time, "settime" for time period
add_to_calendarNoAdd drawing to calendar (default: false)
day_of_the_weekNoDay of week: 1=Sunday through 7=Saturday (for weekly/monthly frequency)
selected_actionYesAction: 1 = Draw Winners only, 2 = Draw Winners & Notify
send_copy_to_meNoEmail notification to account owner (default: false)
how_many_winnersYesNumber of winners to pick (must be >= 1)
include_opted_outNoInclude opted-out participants (default: false)
sweepstakes_tokenYesThe sweepstakes token (UUID format)
week_of_the_monthNoWeek of month: 1-4 (for monthly frequency)
publish_to_winners_pageNoPublish winners to public winners page (default: false)

TDQS

A4.3/5.0
Behavior4/5

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

Despite annotations already marking it as non-readonly, the description adds vital behavioral context: 'CRITICAL: This is a production operation. ALWAYS confirm with the user before scheduling.' It also discloses preconditions like eligible participants and winner count limits, which are not derivable from annotations.

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

Conciseness2/5

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

The description is highly redundant: the opening paragraph is repeated verbatim under '# schedule_drawing' and '## When to use.' The parameter list duplicates the schema's property descriptions without adding value. It is far longer than necessary and lacks front-loading efficiency.

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

Completeness4/5

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

Given the complexity (18 parameters, 8 required), the description covers pre-calls, validations, and critical caveats (production operation, confirmation). It doesn't describe return values, but no output schema exists; still, the overall guidance is substantial enough to invoke the tool correctly.

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 baseline is 3. The description goes beyond schema by adding cross-parameter constraint: 'Winner count cannot exceed available participants' and 'Requires at least one eligible participant.' It also mentions using fetch_timezones for valid IDs, though that's already in schema. Overall, it slightly enriches parameter semantics.

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 'Schedule a future winner drawing for a sweepstakes,' a specific verb and resource. It clearly distinguishes from related tools like draw_winners (immediate) and delete_scheduled_drawing (removal).

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?

Provides explicit pre-calls (fetch_sweepstakes, fetch_groups, fetch_rules), conditions for scheduling (date in future, matches rules), and a critical confirmation requirement. It also instructs to use fetched tokens internally while presenting human-readable info, making usage unambiguous.

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

All Sweeppea MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools follow a clear resource+action pattern (fetch_* for lists, get_* for single items, create/update/delete for writes), making them distinguishable. A few near-overlaps exist (fetch_billing_transactions vs fetch_wallet_transactions, draw_winners vs schedule_drawing) but the descriptions clarify the boundaries.

Naming Consistency4/5

Tool names consistently use snake_case verb_noun, with fetch_ for list operations and get_ for single-item retrieval. Some verb variation (add_participant, count_participants, draw_winners, schedule_drawing) deviates from the dominant create/fetch/update/delete pattern but remains predictable and readable.

Tool Count1/5

With 83 tools, this is far beyond a well-scoped server (typically 3-15, with 25+ considered too many). Even though the platform has broad functionality, the sheer number of tools creates significant agent confusion and selection overhead.

Completeness4/5

The sweepstakes domain is thoroughly covered: lifecycle management, participants, groups, rules, drawings, winners, calendar, notes, todos, tickets, surveys, invoices, billing, files, and entry settings. A few minor gaps exist (e.g., no general participant field update, no archive action) but the surface is remarkably complete for its scope.

Resources