msgraph-mcp

by jspv

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

delete_event

Cancel or delete a calendar event. Specify the user ID when working with shared calendars.

Instructions

Delete or cancel a calendar event. Pass user_id for shared calendars.

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": {
      "event_id": "<event_id>"
    },
    "name": "delete_event"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	No
`event_id`	Yes
`account_id`	No
`cancel_message`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, placing the full burden on the description. It indicates the tool is destructive ('Delete or cancel') but fails to disclose consequences such as irreversibility, notification effects, or permission requirements. The description lacks sufficient behavioral disclosure 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.

Conciseness4/5

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

The description is highly concise at two sentences, with no redundant information. The first sentence clearly states the purpose, and the second adds a useful hint. However, the brevity comes at the cost of omitting important details about parameters and behavior.

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 lack of annotations and 0% parameter descriptions, the description is incomplete. It does not cover return values (despite a known output schema), error scenarios, or behavioral nuances like the difference between delete and cancel. For a destructive tool, more context is needed.

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

Parameters2/5

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

With 0% schema description coverage, the description should compensate but only adds meaning for one parameter ('Pass user_id for shared calendars'). The other parameters (event_id, account_id, cancel_message) are left unexplained, leaving significant gaps in understanding their role and usage.

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?

The description clearly states the tool's purpose: 'Delete or cancel a calendar event.' It uniquely identifies the action and resource, distinguishing it from siblings like create_event, update_event, and respond_to_event. The additional hint about user_id for shared calendars adds specificity.

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

Usage Guidelines3/5

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

The description implies usage by stating the action, but provides no explicit guidance on when to use this tool versus alternatives (e.g., update_event) or when not to use it. The mention of 'Pass user_id for shared calendars' offers context but does not serve as a full usage guideline.

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