moxie-mcp

delete_calendar_event

Delete a specific calendar event using its event ID. Removes the event from your calendar.

Instructions

Delete a calendar event by its event ID

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": {
      "eventId": "<eventId>"
    },
    "name": "delete_calendar_event"
  }
}

Input Schema

Name	Required	Description	Default
`eventId`	Yes	ID of the event to delete (the eventId used in createOrUpdate)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jul 28, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states deletion but does not disclose behavioral traits like irreversibility, side effects, or auth requirements. Adequate for a simple delete but could be more explicit about permanence.

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

Conciseness5/5

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

Single sentence, front-loaded with action and resource, no extraneous words. Perfectly sized for the simple operation.

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

Completeness5/5

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

For a tool with one parameter, no output schema, and no annotations, the description is complete. It tells the agent what it does and how to call it, with the helpful reference to the create/update tool.

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?

Schema has 100% coverage for the only parameter, but the description adds value by referencing 'the eventId used in createOrUpdate', linking to the sibling tool and clarifying the ID source.

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

Purpose5/5

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

Clearly states the verb 'Delete' and resource 'calendar event', with specific identifier 'by its event ID'. Distinguishes from sibling tools which are for other entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context: you have an event ID and want to delete that event. No explicit exclusions or alternatives, but the purpose is straightforward and no sibling tools compete for the same action.

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