Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

delete_participant

DestructiveIdempotent

Permanently delete a participant from a sweepstakes. WARNING: This action cannot be undone. Use get_participant first to verify the participant details before deleting.

delete_participant

When to use

Permanently delete a participant from a sweepstakes. WARNING: This action cannot be undone. Use get_participant first to verify the participant details before deleting.

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)

  • participant_token (string, required) — The participant 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 participant, their entries and their bonus entries. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.
participant_tokenYesThe participant 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 participant, their entries and their bonus entries. 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",
-  "participant_token"
-]New value: +[
+  "sweepstakes_token",
+  "participant_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?

Beyond the destructiveHint=true annotation, the description adds crucial behavioral context: 'cannot be undone', 'DESTRUCTIVE — IRREVERSIBLE', mandatory user confirmation, and a concrete list of what is lost (participant, entries, bonus entries). This materially improves an agent's ability to handle the tool safely.

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 verbatim in the 'When to use' section, and the parameter validation list largely duplicates schema information. The markdown structure and warnings are otherwise efficient, but the redundancy prevents a higher score.

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?

For a destructive 3-parameter delete tool with no output schema, the description covers pre-calls, confirmation requirements, irreversibility, and the exact data lost. Nothing essential for safe invocation 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%, so the baseline is 3. The tool description restates the two token parameters with UUID format but adds no new semantic meaning, and its parameter list omits the confirm parameter entirely. The schema's confirm description is rich, but the tool description itself does not add value beyond it.

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 ('delete'), a specific resource ('participant'), and the containing context ('sweepstakes'), and emphasizes that it is permanent. This clearly differentiates it from the many sibling delete_* tools by object type.

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 includes a dedicated 'When to use' section, mandates get_participant as a pre-call, and requires fetch_sweepstakes when a name is given instead of a token. It also instructs confirming with the user. It does not explicitly contrast with alternative deletion tools, so it falls just short of a 5.

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