delete_calendar_event

Delete macOS Calendar events with a preview to verify details before permanent removal.

Instructions

Delete a calendar event with preview

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)

Registration of delete_calendar_event tool via server.tool() in a loop that registers all TOOLS. The tool is registered with name, description, empty schema {}, and a stub handler.

for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}

server.js:82-86 (handler)

Stub handler function for delete_calendar_event that returns a message indicating this is an inspection stub and the real server is a native macOS binary.

for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}

server.js:24-24 (registration)
Tool name and description defined in the TOOLS array: 'delete_calendar_event' - 'Delete a calendar event with preview'
```
["delete_calendar_event", "Delete a calendar event with preview"],
```

Tool Definition Quality

C2.9/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Mentions 'preview' suggesting a confirmation step, but fails to disclose critical safety details for a destructive operation: whether deletion is permanent or recoverable, handling of recurring events, or what the preview contains.

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?

Extremely brief at 5 words. While front-loaded, the brevity is inappropriate for a destructive operation with no annotations or output schema, leaving dangerous gaps in understanding rather than achieving efficient communication.

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?

Inadequate for a destructive tool with empty input schema and no output schema. Lacks explanation of identification mechanism (how to specify which event), return values, error conditions, or safety constraints required for agent confidence.

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

Parameters4/5

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

Input schema contains 0 parameters, establishing a baseline of 4 per scoring rules. Description neither adds nor subtracts parameter information. However, given the empty schema, the description could have explained how the target event is identified (likely through conversational context).

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 specific verb (Delete) and resource (calendar event), distinguishing it from sibling tools like create_calendar_event and list_calendar_events. The 'with preview' clause adds specific behavioral context, though it could elaborate on 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?

Provides no guidance on when to use this tool versus alternatives, nor any prerequisites (e.g., whether an event must be selected first given the empty parameter schema). No warnings about irreversible actions or conditions for safe use.

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

Install Server

Pilot MCP