Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

delete_group

DestructiveIdempotent

Permanently delete a group from a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, then fetch_groups to get the group_token. WARNING: Cannot delete primary groups, locked groups, or groups with participants.

delete_group

When to use

Permanently delete a group from a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, then fetch_groups to get the group_token. WARNING: Cannot delete primary groups, locked groups, or groups with participants.

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)

  • group_token (string, required) — The group token to delete (UUID format)

Notes

  • DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesMust be true. Set it ONLY after the user explicitly confirmed THIS deletion in this conversation, having been told what is lost: the group and its membership list. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.
group_tokenYesThe group token to delete (UUID format)
sweepstakes_tokenYesThe sweepstakes token (UUID format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true. Set it ONLY after the user explicitly confirmed THIS deletion in this conversation, having been told what is lost: the group and its membership list. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "sweepstakes_token",
-  "group_token"
-]New value: +[
+  "sweepstakes_token",
+  "group_token",
+  "confirm"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag the operation as destructive, but the description adds substantial behavioral detail: deletion is irreversible, confirmation must always be obtained, the group and its membership list are lost, and certain groups cannot be deleted. This goes well beyond what the annotations provide and is especially valuable for a destructive tool.

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

Conciseness3/5

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

The opening sentence is repeated nearly verbatim in the 'When to use' section, creating unnecessary redundancy. The content is well-structured with headings and warnings, and important information is front-loaded, but the duplication keeps it from being tightly concise.

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?

The description covers prerequisites, token acquisition, restrictions, confirmation requirements, and what will be lost. For a destructive 3-parameter tool with no output schema, this is sufficient for an agent to call it safely and correctly. No critical operational context is missing.

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?

Schema description coverage is 100%, and the schema already documents each parameter thoroughly, including a detailed explanation of the confirm flag. The description mostly repeats token formats and validation guidance without adding new semantic meaning. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 states a specific verb and resource: 'Permanently delete a group from a sweepstakes.' This clearly distinguishes it from sibling tools like delete_participant or update_group. The inclusion of restrictions (cannot delete primary/locked groups or groups with participants) further sharpens the tool's identity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear pre-call requirements: use fetch_sweepstakes and fetch_groups to obtain tokens. It also explains when deletion is not possible. However, it does not explicitly name alternatives for related operations, such as delete_participant for removing members or update_group for modifying a group, so it stops short of full when/when-not guidance.

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