Skip to main content
Glama

calendar_delete_event

DestructiveIdempotent

Delete an event from the connected calendar (Google, Outlook or a CalDAV calendar). This action cannot be undone. Use with caution.

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
event_idYesID of the event to delete. Required.
account_idNoCalendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used.
calendar_idNoCalendar ID containing the event. OMIT to use the agent's configured default calendar (or primary).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
send_notificationsNoWhether to send cancellation notifications to attendees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / account_id / description
      Previous value: -"Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used."New value: +"Calendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used."
  2. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used.",
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  4. Added
  5. Removed
  6. Changed2 schema fields changed
    • removedInput schema / properties / calendar_id / default
      Removed value: -"primary"
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID containing the event. Defaults to primary."New value: +"Calendar ID containing the event. OMIT to use the agent's configured default calendar (or primary)."
  7. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so 'cannot be undone' largely restates structured data. It adds nothing about what happens to recurring instances, attendees, or the default-calendar/account resolution, which are the real behavioral questions for a delete.

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

Conciseness3/5

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

Three short sentences, front-loaded with the action and scope, which is good. But 'This action cannot be undone. Use with caution.' is padded warning language that duplicates the destructive annotation rather than earning its place.

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

Completeness3/5

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

For a destructive, open-world tool with five parameters and no output schema, the description covers only the basic action. It omits how default account/calendar selection affects which event is deleted, and that the default is to notify attendees of cancellation — both relevant before an irreversible 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?

Schema description coverage is 100%, so the schema already explains event_id, account_id, calendar_id, in_workspace and send_notifications in detail. The description adds no parameter-level meaning beyond that, which is the baseline case.

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?

States a specific verb and resource ('Delete an event') and names the supported backends (Google, Outlook, CalDAV), so the action is unambiguous. It does not differentiate from calendar-related siblings such as calendar_update_event or explain why one would delete rather than update/cancel.

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?

'Use with caution' is a warning, not usage guidance; it never says when to delete versus updating or declining the event. No prerequisites (permissions, ownership, recurring-event handling) are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.