Skip to main content
Glama

gcal_delete_event

Deletes an event from a connected Google Calendar account, letting your AI assistant remove scheduled entries by event.

Instructions

(Beta) Delete an event of a Google Calendar of a connected Google account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only flags '(Beta)' and mentions a connected account. It does not say whether deletion is permanent or reversible, whether the event is moved to trash, what permissions are required, or how the target event is identified given the empty parameter schema.

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?

A single front-loaded sentence with the beta caveat placed first and no filler. It is efficient, but its brevity comes at the cost of the missing behavioral detail rather than through tight editing of complete information.

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 operation with no annotations, no output schema, and no parameters, the definition is far too thin. An agent cannot determine from it how the event is targeted, whether the action is reversible, or what happens on failure.

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?

The input schema declares zero parameters, so per the baseline this would sit at 4, but the description offers no explanation of how the target event is selected (presumably from conversational or session context). That unresolved targeting question is exactly the semantic detail the description should have supplied.

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 on a Google Calendar belonging to a connected Google account. The platform qualifier distinguishes it from sibling tools like outlook_calendar_delete_event and m365_delete_event, though it doesn't explicitly contrast with them.

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 guidance on when to use this versus delete_calendar_event, m365_delete_event, or the update/create siblings, and no prerequisites such as which account must be connected or what state the event must be in. Usage is only implied by the verb 'Delete' in the name.

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

Deploy Server

Other Tools