Skip to main content
Glama

graph_cancel_event

Cancel a meeting you organize and send a cancellation notice to all attendees, with an optional comment. Use when the organizer needs to call off an event rather than silently delete it.

Instructions

Cancel a meeting you organize and notify the attendees.

Unlike graph_delete_event, which removes the event without telling anyone, cancelling sends a cancellation notice to every attendee. Only the organizer can cancel a meeting; attendees should decline with graph_respond_to_event instead.

Args: event_id: The event ID to cancel. comment: Optional note to include in the cancellation notice. user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

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": "graph_cancel_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
commentNo
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the side effect (cancellation notice to every attendee), the organizer-only restriction, and the delegated permission requirements for cross-calendar use. It stops short of saying whether cancellation is reversible, how recurring events or instances are handled, or what the call returns.

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?

Front-loaded with the core behavior and the sibling contrast before the parameter list; every sentence adds information, and the Args block is justified because the schema has no descriptions.

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

Completeness4/5

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

For a no-annotation mutation tool with no output schema and undocumented parameters, this covers safety behavior, permission prerequisites, and alternatives well. The remaining gap is return/confirmation behavior and edge cases such as recurring meetings or cancellation of already-declined events.

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 description coverage is 0%, but the description compensates by documenting all three parameters, including that an empty user value targets your own calendar and that it requires Calendars.Read.Shared or Calendars.ReadWrite.Shared. It does not state the expected event_id format or how a comment is rendered in the notice.

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?

States a specific verb and resource ('Cancel a meeting you organize and notify the attendees') and immediately contrasts with graph_delete_event, which 'removes the event without telling anyone.' An agent can distinguish cancel-with-notice from silent delete without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this only if you are the organizer; attendees should use graph_respond_to_event instead; use graph_delete_event if no notice should be sent. Both alternatives and the exclusion condition are named.

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

Deploy Server

Other Tools