Skip to main content
Glama

Create event

create_event

Create calendar events and meetings in Microsoft 365, email invitations to attendees immediately, and optionally add a Microsoft Teams link.

Instructions

Create a calendar event. If attendees are given this is a meeting and invitations are emailed to them immediately. Set isOnlineMeeting to add a Microsoft Teams link (if the tenant allows it).

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": "<start>"
    },
    "name": "create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd. ISO 8601. With an offset (2026-11-02T14:00:00Z or +01:00) it is exact; without one it is local time in timeZone, or in the mailbox time zone if timeZone is omitted. For all-day events the day after the last day (exclusive)
bodyNoDescription / agenda
startYesStart. ISO 8601. With an offset (2026-11-02T14:00:00Z or +01:00) it is exact; without one it is local time in timeZone, or in the mailbox time zone if timeZone is omitted. For all-day events a date (YYYY-MM-DD)
showAsNoFree/busy status
subjectYesTitle
calendarNoCalendar (default: the main calendar). Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders
isAllDayNoAll-day event
locationNoLocation text
timeZoneNoIANA time zone for start/end without an offset, e.g. "Europe/London"
attendeesNoRequired attendees: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bodyFormatNoBody format: "text" (default) or "html"
categoriesNoCategory names
recurrenceNoMake the event repeat
sensitivityNo
isOnlineMeetingNoAdd a Teams meeting link
optionalAttendeesNoOptional attendees: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
reminderMinutesBeforeNoReminder in minutes before start; null disables the reminder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing a real side effect: supplying attendees immediately emails invitations, which is not inferable from destructiveHint=false and is important because it cannot be unsent. It also flags a conditional capability (Teams link only if the tenant allows it). It stops short of covering the recurrence or failure behavior of a 17-parameter mutation.

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?

Three short sentences, front-loaded with the core action and followed by the two behaviors an agent could otherwise get wrong. Every clause carries information; nothing is redundant with the title or 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 17-parameter tool with a nested recurrence object and no output schema, the description covers the highest-risk behaviors (invitations sent, Teams dependency). Remaining gaps, such as permission requirements and what is returned on success, are modest given the rich schema descriptions.

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?

Schema coverage is 94%, so the schema already documents nearly every parameter in detail, including the ISO 8601 offset rules. The description only adds meaning for two of them (attendees as a meeting trigger, isOnlineMeeting as a Teams link), so it sits at the high-coverage baseline.

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?

Opens with a specific verb+resource ("Create a calendar event"), which cleanly separates it from siblings like create_contact or create_draft. It does not explicitly contrast with update_event, but the create/update distinction is carried by the verb itself.

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?

Usage is implied through conditional behavior ("If attendees are given this is a meeting") rather than stated as when-to-use guidance. There is no explicit statement of when to choose this over update_event or respond_to_event, and no prerequisites such as calendar write permission.

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