gcal

delete_event

Destructive

Permanently delete an event by eventId (no undo). Sends cancellation notifications to attendees by default (control with sendUpdates). Returns {success: true, eventId, message} on success.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`eventId`	Yes	Event ID to delete
`calendarId`	Yes	Calendar ID from list_calendars
`sendUpdates`	No	Whether to send cancellation notifications (all: notify all attendees, externalOnly: only non-Google Calendar users, none: no notifications)	all

Output Schema

TableJSON Schema

Name	Required	Description	Default
`eventId`	Yes
`message`	Yes
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedApr 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedFeb 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "eventId": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "eventId",
+    "message"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by stating 'permanently delete' and 'no undo'. It adds valuable context beyond annotations: default behavior of sending cancellation notifications and the ability to control it via sendUpdates, though it doesn't mention rate limits or auth needs.

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?

The description is front-loaded with the core action and key details ('permanently delete', 'no undo', notifications), followed by return value info. Every sentence adds value without redundancy, making it efficient and well-structured.

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?

Given the presence of annotations (destructiveHint, readOnlyHint), a rich input schema with 100% coverage, and an output schema (implied by return value description), the description is complete. It covers the tool's behavior, key parameters, and output, leaving no significant gaps for a deletion tool.

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?

With 100% schema description coverage, the schema fully documents parameters like eventId, calendarId, and sendUpdates with enum details. The description adds minimal semantics by mentioning eventId and sendUpdates control, but doesn't provide extra meaning beyond the schema's thorough descriptions.

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 clearly states the specific action ('permanently delete') and resource ('an event by eventId'), distinguishing it from siblings like update_event or create_event. It explicitly mentions the irreversible nature ('no undo'), which further clarifies its purpose.

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 implies usage for deleting events, with context from siblings suggesting alternatives like update_event for modifications or get_calendar_events for viewing. However, it lacks explicit guidance on when to use this tool versus others (e.g., no mention of prerequisites like needing eventId from list operations).

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

All gcal tools Inspect

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.