Skip to main content
Glama

calendar delete event

calendar_delete_event
DestructiveIdempotent

Deletes a specified Google Calendar event from the primary or chosen calendar, with optional attendee updates and mandatory confirmation before removal.

Instructions

Delete a calendar event. Requires confirm=true.

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": {
      "event_id": "<event_id>"
    },
    "name": "calendar_delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
event_idYes
calendar_idNoprimary
send_updatesNonone

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description does add one genuinely useful behavioral fact — that confirm=true is mandatory even though the schema defaults it to false — but it omits what happens when confirm is false (error vs no-op), whether deletion is permanent, and whether attendees are notified.

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

Conciseness4/5

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

Two short sentences with the destructive action stated first and the required gate second, so nothing is wasted. The brevity is efficient rather than padded, though it edges toward under-specification for a destructive tool.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with four undocumented parameters and no schema coverage, the definition does far too little; an output schema exists so return values needn't be described, but the confirm semantics, permanence, and send_updates behavior are all missing. An agent could invoke it but would be guessing about side effects on attendees and calendars.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must compensate and largely fails. It covers only the confirm gate; event_id, calendar_id (default "primary"), and especially send_updates — whose values determine whether attendees are emailed — are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("Delete a calendar event"), which clearly separates it from calendar_create_event, calendar_update_event, and calendar_get_event. It stops short of explicitly naming any sibling or scope constraint, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no mention of when deletion is preferable to updating, no prerequisites, no note about recurring events or whether the event moves to trash. The only condition given (confirm=true) is a mechanical gate, not usage guidance.

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