Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

fetch_sweepstakes

Read-onlyIdempotent

Get the sweepstakes associated with your account. Returns a paginated SUMMARY by default (token, name, handler, type, dates, timezone, status, archived, and a computed state). STATE: each item carries state — "scheduled" (not started), "running" (open now), or "ended" (end date already passed) — plus has_ended and days_until_end. ALWAYS read state before giving operational advice: never tell the user to share the entry link or wait for participants on a sweepstakes whose state is "ended". PAGINATION: use page and page_size (default 25, max 100). The response carries pagination.total, total_pages and has_more — if has_more is true, either request the next page or tell the user how many were not shown. NEVER invent sweepstakes that are not in the response. HEAVY PAYLOAD: include_settings: true adds the full Settings object (SMS/email templates, ~1.5 KB each) — only request it when the user asks about entry page settings or message templates, and prefer get_entry_settings for a single sweepstakes. Use tokens internally for tool chaining but present only human-readable information (names, dates, statuses) to the user.

fetch_sweepstakes

When to use

Get the sweepstakes associated with your account. Returns a paginated SUMMARY by default (token, name, handler, type, dates, timezone, status, archived, and a computed state). STATE: each item carries state — "scheduled" (not started), "running" (open now), or "ended" (end date already passed) — plus has_ended and days_until_end. ALWAYS read state before giving operational advice: never tell the user to share the entry link or wait for participants on a sweepstakes whose state is "ended". PAGINATION: use page and page_size (default 25, max 100). The response carries pagination.total, total_pages and has_more — if has_more is true, either request the next page or tell the user how many were not shown. NEVER invent sweepstakes that are not in the response. HEAVY PAYLOAD: include_settings: true adds the full Settings object (SMS/email templates, ~1.5 KB each) — only request it when the user asks about entry page settings or message templates, and prefer get_entry_settings for a single sweepstakes. Use tokens internally for tool chaining but present only human-readable information (names, dates, statuses) to the user.

Parameters to validate before calling

  • page (number, optional) — range: 1–+∞ — Page number, 1-based. Default: 1.

  • page_size (number, optional) — range: 1–100 — Sweepstakes per page. Default: 25, maximum: 100.

  • include_settings (boolean, optional) — Include the full Settings object of each sweepstakes (heavy: ~1.5 KB each, mostly SMS/email templates). Default: false.

  • include_archived (boolean, optional) — Include archived sweepstakes. Default: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based. Default: 1.
page_sizeNoSweepstakes per page. Default: 25, maximum: 100.
include_archivedNoInclude archived sweepstakes. Default: true.
include_settingsNoInclude the full Settings object of each sweepstakes (heavy: ~1.5 KB each, mostly SMS/email templates). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / include_archived
      Added value: +{
+  "description": "Include archived sweepstakes. Default: true.",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_settings
      Added value: +{
+  "description": "Include the full Settings object of each sweepstakes (heavy: ~1.5 KB each, mostly SMS/email templates). Default: false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number, 1-based. Default: 1.",
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Sweepstakes per page. Default: 25, maximum: 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses meaningful behavioral details: pagination fields and has_more handling, the semantics of state, the heavy cost of include_settings, and a strong 'NEVER invent sweepstakes' rule. These are exactly the non-obvious behaviors an agent needs to avoid mistakes.

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 main body is duplicated verbatim: the same long paragraph appears twice, once under DESCRIPTION and once under '# fetch_sweepstakes ## When to use'. The parameter section also repeats schema content. While the content is organized and front-loaded, the redundancy makes it significantly longer than it needs to be.

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 having no output schema, the description thoroughly explains the response shape, state values, pagination metadata, default behavior, and heavy-payload tradeoffs. It gives an agent everything needed to call the tool correctly and interpret results safely.

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. The description adds some value beyond the schema by explaining when include_settings should and should not be used, and by framing pagination parameters around the response's has_more field. However, the dedicated 'Parameters to validate' section largely duplicates the schema text.

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 uses a specific verb and resource: 'Get the sweepstakes associated with your account.' It also clarifies the default return shape (a paginated SUMMARY with a computed state), which distinguishes it from sibling fetch tools. Mentioning get_entry_settings as the preferred alternative for single-sweepstakes settings further disambiguates it.

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?

It has an explicit 'When to use' section and provides concrete routing guidance: prefer get_entry_settings for a single sweepstakes, only request include_settings when the user asks about entry page settings or message templates, and read state before giving operational advice. This is clear when-to-use and when-not-to-use direction.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources