Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp

create_rule

Create a new official rules document for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. LEGAL BYPASS WARNING: This tool publishes a free-form document WITHOUT the legal safeguards of create_rules_wizard (AMOE enforcement, 21+ alcohol gate, COPPA, state eligibility clauses). ALWAYS prefer create_rules_wizard, which generates certified legal templates server-side. Use this tool ONLY when the user already has a complete, professionally reviewed rules document. NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before publishing — exactly as with delete_* tools — and confirm the document was prepared or reviewed by the user or their counsel. SECONDARY RULES WARNING: Before creating rules, call fetch_rules to check if the sweepstakes already has primary rules. If primary rules already exist, WARN the user that the new rules will be created as SECONDARY and will NOT be the ones published on the Entry Page or assigned to the short URL (swpp.me/r/[handler]). The short URL always points to the primary rules. The user can change which rules are primary in the Official Rules section of the app. Only proceed after the user acknowledges this.

create_rule

When to use

Create a new official rules document for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. LEGAL BYPASS WARNING: This tool publishes a free-form document WITHOUT the legal safeguards of create_rules_wizard (AMOE enforcement, 21+ alcohol gate, COPPA, state eligibility clauses). ALWAYS prefer create_rules_wizard, which generates certified legal templates server-side. Use this tool ONLY when the user already has a complete, professionally reviewed rules document. NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before publishing — exactly as with delete_* tools — and confirm the document was prepared or reviewed by the user or their counsel. SECONDARY RULES WARNING: Before creating rules, call fetch_rules to check if the sweepstakes already has primary rules. If primary rules already exist, WARN the user that the new rules will be created as SECONDARY and will NOT be the ones published on the Entry Page or assigned to the short URL (swpp.me/r/[handler]). The short URL always points to the primary rules. The user can change which rules are primary in the Official Rules section of the app. Only proceed after the user acknowledges this.

Pre-calls required

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

  2. fetch_rules(sweepstakes_token) — if primary rules exist, WARN that the new one will be SECONDARY

Parameters to validate before calling

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

  • title (string, required) — Title of the official rules document (max 100 characters)

  • document_content (string, required) — Full HTML content of the official rules (max 1,000,000 characters)

Notes

  • Prefer create_rules_wizard for legal-grade Official Rules

  • Use this only when you have a fully prepared HTML document and the wizard does not apply

  • This tool bypasses the wizard safeguards (AMOE, 21+ alcohol gate, COPPA, state eligibility) — require explicit user confirmation before publishing, like delete_* tools, and confirm the document was prepared or reviewed by the user or their counsel

  • NEVER compose or modify the legal language yourself

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the official rules document (max 100 characters)
document_contentYesFull HTML content of the official rules (max 1,000,000 characters)
sweepstakes_tokenYesThe sweepstakes token (UUID format)

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate this is not read-only and not idempotent. The description goes far beyond by disclosing the 'LEGAL BYPASS WARNING' regarding missing safeguards (AMOE, 21+, COPPA, state eligibility), requiring explicit user confirmation like delete_* tools, and explaining the secondary rules consequence where the new rules won't be published on the Entry Page or short URL. This is rich behavioral context that helps the agent anticipate side effects. No contradiction with 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 significantly redundant. The legal warning is repeated nearly verbatim three times, and the pre-call list appears both in the introductory paragraph and under 'Pre-calls required.' While the section headers provide structure, the duplication violates conciseness—several sentences could be removed without losing 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?

Despite verbosity, the description covers all necessary context for a high-stakes, legally sensitive tool: prerequisites (fetch_sweepstakes, fetch_rules), parameter validation, alternative tools, side effects (secondary rules/URL behavior), user confirmation requirement, and warnings against composing legal language. It is complete for an agent to use safely and 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?

The schema already provides 100% parameter coverage with descriptions for all three parameters. The description adds meaningful context beyond the schema: the sweepstakes_token should come from fetch_sweepstakes, document_content must be full HTML, and parameters require validation (e.g., title max 100 chars). While not necessary, this extra guidance aids correct invocation.

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 clearly states the action: 'Create a new official rules document for a sweepstakes.' It also distinguishes itself from the sibling tool create_rules_wizard by emphasizing that this tool publishes a free-form document without wizard safeguards. This is a specific verb+resource with clear differentiation from alternatives.

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 when-to-use and when-not-to-use guidance: 'ALWAYS prefer create_rules_wizard... Use this tool ONLY when the user already has a complete, professionally reviewed rules document.' It also mandates pre-calls (fetch_sweepstakes, fetch_rules) and explains the secondary rules behavior, giving clear context for when this tool is appropriate versus alternatives.

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