Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

delete_calendar_event

DestructiveIdempotent

Permanently delete a calendar event. Use fetch_calendar_events first to get the event_token. WARNING: This action cannot be undone.

delete_calendar_event

When to use

Permanently delete a calendar event. Use fetch_calendar_events first to get the event_token. WARNING: This action cannot be undone.

Parameters to validate before calling

  • event_token (string, required) — The event 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 calendar event and its reminders. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.
event_tokenYesThe event token to delete (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 calendar event and its reminders. 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: -[
-  "event_token"
-]New value: +[
+  "event_token",
+  "confirm"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this as destructive and not read-only. The description adds meaningful context beyond that: irreversibility, the warning that it cannot be undone, and the requirement to confirm with the user and explain what will be lost. This aligns with and enriches the annotations.

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 description is repetitive: the opening paragraph is duplicated verbatim under the '# delete_calendar_event' and '## When to use' headings. It also restates parameter information already present in the schema. While the structure is organized, the redundancy prevents a higher score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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, irreversibility, and user confirmation. The schema covers the required confirm parameter in detail. Minor omissions like return behavior are not critical for this operation, so the definition is largely complete.

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 value by telling the agent how to obtain event_token via fetch_calendar_events, which is not in the schema. The confirm parameter is thoroughly documented in the schema itself.

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 calendar event.' It clearly distinguishes this from sibling tools like create_calendar_event, get_calendar_event, and update_calendar_event by emphasizing permanence and deletion.

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?

It explicitly instructs to use fetch_calendar_events first to obtain the event_token and mandates user confirmation before calling. It does not explicitly name non-destructive alternatives, but the prerequisite and confirmation guidance make the intended usage clear.

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