fastmcp-gsuite

Overview Schema Source Related Servers Discussions Admin

delete_calendar_event

Delete a calendar event by specifying the Google account email, calendar ID, and event ID. Removes events from Google Calendar through natural language interactions.

Instructions

Delete an event from a calendar.

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": {
      "user_id": "<user_id>",
      "calendar_id": "<calendar_id>",
      "event_id": "<event_id>"
    },
    "name": "delete_calendar_event"
  }
}

Input Schema

Name	Required	Description
`user_id`	Yes	The EMAIL of the Google account. Choose from:
`calendar_id`	Yes	The ID of the calendar containing the event (use 'primary' for the primary calendar).
`event_id`	Yes	The unique ID of the event to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 21, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It states 'Delete an event' but does not explain whether the deletion is permanent, reversible, or what happens to attendees. This is insufficient for a mutation tool.

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?

The description is very concise at one sentence, but it could be more informative without being verbose. It is not overly long, but it lacks structure and depth, making it lean toward underspecification rather than effective conciseness.

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?

Given the tool has three required parameters and sibling tools for related actions, the description is incomplete. It does not mention what happens after deletion (e.g., no return value), nor does it provide any usage context. The simplicity of the operation does not excuse the lack of basic behavioral information.

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 already describes all three parameters (user_id, calendar_id, event_id) with clear descriptions. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate given 100% schema coverage.

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 clearly states the action 'Delete' and the resource 'an event from a calendar', which distinguishes it from sibling tools like 'create_calendar_event' or 'update_calendar_event'. However, it does not specify the scope (e.g., permanent vs. trash), which would enhance clarity.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not mention that deletion is irreversible or that the event must exist. No context about prerequisites or consequences is given.

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