Skip to main content
Glama

delete_event

Remove or cancel a calendar event in Microsoft Outlook by specifying the account and event IDs. Optionally send cancellations to attendees for efficient event management.

Instructions

Delete or cancel a calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYes
event_idYes
send_cancellationNo

Implementation Reference

  • The handler function for the 'delete_event' tool, decorated with @mcp.tool for automatic registration in FastMCP. It deletes a calendar event either by sending a cancellation (if send_cancellation=True) or permanent deletion using Microsoft Graph API endpoints.
    @mcp.tool
    def delete_event(
        account_id: str, event_id: str, send_cancellation: bool = True
    ) -> dict[str, str]:
        """Delete or cancel a calendar event"""
        if send_cancellation:
            graph.request("POST", f"/me/events/{event_id}/cancel", account_id, json={})
        else:
            graph.request("DELETE", f"/me/events/{event_id}", account_id)
        return {"status": "deleted"}
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Delete or cancel') but doesn't clarify the difference between deletion and cancellation, whether this requires specific permissions, if the action is reversible, what happens to attendees, or any rate limits. For a destructive operation, this leaves critical behavioral traits unspecified.

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?

The description is extremely concise—a single, clear sentence that front-loads the core action and resource. There is no wasted language or unnecessary elaboration, making it efficient and easy to parse.

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's complexity (a destructive operation with 3 parameters), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't address behavioral nuances, parameter meanings, or expected outcomes, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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 description adds no parameter semantics beyond what the input schema provides. With 0% schema description coverage, the schema only lists parameter names and types without explaining their meaning. The description doesn't compensate by explaining what 'account_id', 'event_id', or 'send_cancellation' do, leaving parameters largely undocumented. Baseline 3 applies as the schema provides some structure, but value addition is minimal.

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 or cancel') and resource ('a calendar event'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_contact' or 'delete_file' by specifying the event resource, though it doesn't explicitly differentiate from similar operations like 'respond_event' which might also modify event status.

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. It doesn't mention prerequisites (e.g., needing authentication first), contrast with 'update_event' for modifications instead of deletion, or specify scenarios where deletion is appropriate versus cancellation. The description alone offers no usage context.

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

Related 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/elyxlz/microsoft-mcp'

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