Skip to main content
Glama

delete_calendar_event

Preview and delete calendar events to keep your schedule clean. Remove unwanted events with a single action.

Instructions

Delete a calendar event with preview

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:23-23 (registration)
    Tool 'delete_calendar_event' is registered as part of the TOOLS array with description 'Delete a calendar event with preview'. The actual implementation is not present in this stub file — it's a native binary.
    ["delete_calendar_event", "Delete a calendar event with preview"],
Behavior2/5

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

No annotations are present, so the description must convey behavioral traits. It only states 'delete... with preview', leaving unclear whether events are permanently deleted, moved to trash, or require confirmation. No side effects or permissions are disclosed.

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

Conciseness2/5

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

The description is extremely short (one phrase) but lacks structure. It does not front-load key information such as how to specify which event to delete. It sacrifices completeness for brevity.

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

Completeness1/5

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

Given the absence of input parameters and output schema, the description fails to provide necessary context about how the tool operates. It does not explain how the event is selected, what 'preview' means, or what happens after deletion. This is insufficient for correct invocation.

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

Parameters1/5

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

The input schema has zero parameters, which is unusual for a delete operation. The description does not explain how the target event is identified (e.g., by ID, selection, or context). This is a critical gap, and the description adds no value beyond the empty schema.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the action 'delete' and resource 'calendar event', clearly indicating the tool's purpose. However, the phrase 'with preview' is ambiguous and does not clarify what the preview entails.

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?

No guidance is provided on when to use this tool versus alternatives like 'update_calendar_event' or 'create_calendar_event'. There is no mention of prerequisites, context, or conditions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server