Skip to main content
Glama

Delete or cancel event

delete_event
Destructive

Deletes a calendar event by ID and can notify attendees or permanently skip Deleted Items. Use for meetings you organize; decline others' meetings with respond_to_event.

Instructions

Delete an event. For meetings you organize, attendees are sent a cancellation unless notifyAttendees is false. To decline someone else's meeting, use respond_to_event instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent ID
permanentNoSkip Deleted Items (default false)
notifyAttendeesNoSend cancellations to attendees (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add consequence detail — which it does by disclosing that attendees receive cancellations and that notifyAttendees can suppress them. The one gap is that it never mentions the permanent flag's effect (skipping Deleted Items), so recoverability of the deletion is left to the schema field.

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

Conciseness5/5

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

Three short sentences, action first, side effect second, alternative route last. No filler and nothing buried.

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 three-parameter tool with no output schema, the description covers purpose, attendee side effect, and the correct alternative. It is only slightly short on the permanent/soft-delete distinction, which the schema field covers but the description never reinforces.

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 coverage is 100%, so all three parameters are already documented with defaults in the schema. The description restates notifyAttendees' effect in prose but adds no format or edge-case detail beyond that, and says nothing about permanent — baseline 3 is appropriate when the schema carries the load.

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?

"Delete an event" states a specific verb and resource, and the following sentences immediately distinguish this operation from declining an invitation by naming respond_to_event. An agent can tell delete vs decline apart without opening any schema.

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?

The description gives an explicit routing rule: to decline someone else's meeting, use respond_to_event instead. It also states the condition under which attendees are not notified, so the agent knows both when to call this tool and when to avoid it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.