Skip to main content
Glama

graph_create_event

Create a calendar event with title, start/end times, timezone, attendees, location, recurrence, reminders, and optional Teams online meeting.

Instructions

Create a new calendar event.

Args: subject: Event subject/title. start_datetime: Start time in ISO 8601 (e.g. "2025-03-01T10:00:00"). end_datetime: End time in ISO 8601 (e.g. "2025-03-01T11:00:00"). timezone: Timezone (default "UTC"). Examples: "Pacific Standard Time", "Europe/London". body: Optional event body/description. location: Optional location name. attendees: Optional list of required attendee email addresses. is_online_meeting: Whether to create a Teams online meeting (default false). is_html: Whether the body is HTML (default: plain text). is_all_day: Whether the event lasts all day (default false). Graph expects midnight start and end times for all-day events. show_as: Free/busy status: "free", "tentative", "busy", "oof", "workingElsewhere", or "unknown" (default "busy"). sensitivity: Sensitivity: "normal", "personal", "private", or "confidential" (default "normal"). reminder_minutes_before_start: Reminder lead time in minutes. Negative keeps the mailbox default (default -1). optional_attendees: Optional list of optional attendee email addresses. categories: Outlook category names to tag the event with. allow_new_time_proposals: Whether attendees may propose new times (default true). response_requested: Whether attendees are asked to respond (default true). repeat: Recurrence pattern: "none", "daily", "weekly", "monthly", or "yearly" (default "none"). repeat_interval: Interval between occurrences (default 1). repeat_days: Weekday names for weekly recurrence, e.g. ["monday", "thursday"]. Required when repeat is "weekly". repeat_until: Last date of the recurrence (YYYY-MM-DD). Mutually exclusive with repeat_count. repeat_count: Number of occurrences. Mutually exclusive with repeat_until. 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": {
      "subject": "<subject>",
      "start_datetime": "<start_datetime>",
      "end_datetime": "<end_datetime>"
    },
    "name": "graph_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
userNo
repeatNonone
is_htmlNo
show_asNobusy
subjectYes
locationNo
timezoneNoUTC
attendeesNo
categoriesNo
is_all_dayNo
repeat_daysNo
sensitivityNonormal
end_datetimeYes
repeat_countNo
repeat_untilNo
start_datetimeYes
repeat_intervalNo
is_online_meetingNo
optional_attendeesNo
response_requestedNo
allow_new_time_proposalsNo
reminder_minutes_before_startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose real behavior: delegated-permission requirements for the 'user' arg, Graph's expectation of midnight start/end for all-day events, mutual exclusivity of repeat_until and repeat_count, and that a negative reminder value keeps the mailbox default. However, it never states side effects an agent must anticipate — whether attendees receive invitations, what happens on scheduling conflicts, or what the call returns (e.g., an event ID needed for follow-up calls).

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?

It is long, but the length is driven by 23 parameters and each line adds information rather than restating the schema verbatim. The purpose line is front-loaded and the args are ordered with required fields first. Minor waste comes from repeating defaults already present in the schema.

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 23-parameter mutation tool with no annotations and no output schema, the description is thorough on inputs and constraints. The remaining gap is outcome-level: no statement of what is returned or how invitations to attendees are dispatched, which matters for a create-and-notify operation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate entirely, and it does: every one of the 23 parameters gets meaning, format, default, or constraint. Highlights include ISO 8601 examples for the datetimes, concrete timezone examples, enumerated show_as/sensitivity/repeat values, the conditional rule that repeat_days is required when repeat='weekly', and the repeat_until/repeat_count exclusion.

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 opening line states a specific verb and resource: 'Create a new calendar event.' An agent can immediately tell this is the creation counterpart to graph_update_event, graph_delete_event, and graph_cancel_event. It stops short of an explicit boundary against graph_create_online_meeting, which also creates a calendar artifact, so it is clear but not sibling-differentiated.

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?

There is no when-to-use / when-not-to-use guidance and no named alternative. The only prerequisite-like content is buried in the 'user' arg ('Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions'), which covers auth for one parameter but says nothing about choosing this tool over graph_create_online_meeting or graph_update_event.

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