Skip to main content
Glama

Create Calendar Event

create_event
Destructive

Creates a new Microsoft 365 calendar event so you can schedule meetings or appointments with subject, start time, attendees, location, reminders, and Teams links.

Instructions

Create a new calendar event

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 date/time (ISO format). Required unless all_day is true; then it is the last day (YYYY-MM-DD, inclusive) and defaults to start.
bodyNoEvent description
startYesStart date/time (ISO format), or the first day (YYYY-MM-DD) when all_day is true
all_dayNoAll-day event: start and end are dates (YYYY-MM-DD) and end is the last day, inclusive. Set time_zone to the calendar's zone (e.g. Australia/Perth). Default: false.
show_asNoHow the time shows in free/busy: free, tentative, busy, oof (out of office) or workingElsewhere. Default follows Outlook: free for an all-day event, busy for a timed one.
subjectYesEvent subject/title
is_draftNoSave to your calendar without inviting attendees (any attendees param is ignored). Add attendees and send the meeting later from Outlook. Default: false.
locationNoEvent location
reminderNofalse turns the event's reminder off; true turns it on. Omit to leave it as it is.
attendeesNoComma-separated email addresses of attendees
time_zoneNoZone of start and end, IANA or Windows name (default: UTC). The reply shows the event's times in it too.
calendar_idNoID of the calendar to use, from list_calendars. Omit for your default calendar.
content_typeNoBody content type: Text or HTML (default: Text)
online_meetingNoAdd a Teams meeting to the event; joinUrl is returned in the event details (default: false)
reminder_minutesNoMinutes before the start to remind, which also turns the reminder on. For an all-day event the start is midnight, so 1080 reminds at 6 pm the evening before. Graph's default is 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's job is to explain consequences: that attendee invites are sent and the meeting is destructive-ish, that is_draft suppresses invites, and that reminders default to 15 minutes. None of this appears; the description repeats the title and adds zero behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is one short, front-loaded sentence with no wasted words, but the brevity is under-specification rather than economy — six words is not appropriately sized for a 15-parameter creation tool.

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?

A 15-parameter mutation tool with no output schema and a destructiveHint=true annotation needs the description to explain side effects (invites, Teams meeting creation, reminder defaults). With only 'Create a new calendar event', the definition is far too thin relative to the tool's complexity, even though the schema compensates for parameter detail.

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 description coverage is 100% and every one of the 15 parameters carries a detailed description (end/all_day interaction, show_as defaults, time_zone format, is_draft semantics). The description itself adds nothing about parameters, but the baseline of 3 applies because the schema does the full job.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a verbatim restatement of the name and title ('Create Calendar Event' / 'Create a new calendar event'), adding no scope, no resource detail, and no distinction from siblings such as update_event or create_draft. Only the bare verb+resource is conveyed.

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 guidance, no prerequisite (e.g. needing a calendar_id from list_calendars or a time_zone), and no routing to alternatives like update_event for existing events or list_calendar_view to check conflicts. An agent must infer all of this from the schema alone.

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