Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

delete_rule

DestructiveIdempotent

Permanently delete an official rules document from a sweepstakes. Use fetch_rules first to get the rules_token. WARNING: This action cannot be undone.

delete_rule

When to use

Permanently delete an official rules document from a sweepstakes. Use fetch_rules first to get the rules_token. WARNING: This action cannot be undone.

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 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 Official Rules document and its public URL. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.
rules_tokenYesThe rules 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 Official Rules document and its public URL. 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",
-  "rules_token"
-]New value: +[
+  "sweepstakes_token",
+  "rules_token",
+  "confirm"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description repeatedly warns that the action is destructive and irreversible, and the Notes instruct to always confirm and explain what will be lost. These behavioral details align with the destructiveHint annotation and add the user-confirmation context beyond the structured flags.

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 content is front-loaded with the warning, but the first paragraph is duplicated almost verbatim under 'When to use,' and the irreversible/destructive warning appears three times. This redundancy makes the description longer than necessary without adding new 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?

For a destructive delete operation, the description covers prerequisites, parameter validation, confirmation requirements, and the irreversible nature of the action. The schema's confirm description supplies the exact loss explanation, and no output schema is needed for a delete call.

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?

The schema provides 100% parameter coverage, including UUID formats and a thorough confirm contract, so the description does not need to add much. Its parameter list mostly restates the schema's existing descriptions rather than adding new semantic meaning, which meets the baseline for fully covered schemas.

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 opens with a specific verb and object: 'Permanently delete an official rules document from a sweepstakes.' This clearly distinguishes delete_rule from the many other delete_* siblings and names the exact resource affected.

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 provides explicit when-to-use guidance, a required pre-call to fetch_rules for the rules_token, and a conditional pre-call to fetch_sweepstakes when a name is supplied instead of a token. It also instructs to confirm with the user before calling, leaving no ambiguity about prerequisites.

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