Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp

update_rule

Idempotent

Update an existing official rules document. Use fetch_rules first to get the rules_token. LEGAL BYPASS WARNING: Updating document_content replaces a legally valid document with free-form HTML that bypasses every safeguard of create_rules_wizard (AMOE, 21+ alcohol gate, COPPA, state eligibility). NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before replacing document_content — exactly as with delete_* tools — and confirm the replacement was prepared or reviewed by the user or their counsel. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation.

update_rule

When to use

Update an existing official rules document. Use fetch_rules first to get the rules_token. LEGAL BYPASS WARNING: Updating document_content replaces a legally valid document with free-form HTML that bypasses every safeguard of create_rules_wizard (AMOE, 21+ alcohol gate, COPPA, state eligibility). NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before replacing document_content — exactly as with delete_* tools — and confirm the replacement was prepared or reviewed by the user or their counsel. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation.

Pre-calls required

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

Parameters to validate before calling

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

  • rules_token (string, required) — The rules token to update (UUID format)

  • title (string, optional) — New title for the rules document (max 100 characters)

  • document_content (string, optional) — New HTML content for the rules (max 1,000,000 characters)

  • abbreviated_rules_shopify (string, optional) — Abbreviated rules for Shopify integration (max 1,000,000 characters)

Notes

  • Replacing document_content swaps a legally valid document for free-form HTML that bypasses the wizard safeguards — require explicit user confirmation first, like delete_* tools

  • NEVER compose or modify the legal language yourself

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title for the rules document (max 100 characters)
rules_tokenYesThe rules token to update (UUID format)
document_contentNoNew HTML content for the rules (max 1,000,000 characters)
sweepstakes_tokenYesThe sweepstakes token (UUID format)
abbreviated_rules_shopifyNoAbbreviated rules for Shopify integration (max 1,000,000 characters)

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate idempotentHint and openWorldHint but no destructive hint. The description goes far beyond annotations by warning that updating document_content replaces a legally valid document with free-form HTML that bypasses safeguards, requiring explicit user confirmation. It clearly discloses the legal bypass risk and behavioral safeguards.

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?

The description is well-structured with clear sections (When to use, Pre-calls, Parameters, Notes) and front-loaded critical warnings. However, there is some repetition (legal warning appears twice), which slightly decreases conciseness.

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?

Given the high complexity (5 parameters, legal implications, no output schema), the description covers prerequisites (fetch_sweepstakes), parameter validation details, behavioral warnings, and field constraints comprehensively. It is complete for safe and correct tool invocation.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by clarifying which fields are updatable and which are not, plus max lengths and format notes (UUID). It explains constraints beyond the schema, such as the legal implications for document_content.

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 it updates an existing official rules document, specifying updatable fields (title, document_content, abbreviated_rules_shopify) and non-updatable fields, distinguishing it from sibling tools like create_rule and create_rules_wizard.

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?

Explicitly tells when to use (update existing rule), prerequisite (fetch_rules first), safety warnings (never compose legal language, require user confirmation like delete_* tools), and what not to do (don't tell user about unsupported fields).

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