Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_create_event

Create a calendar event with optional attendees, recurrence, and Teams online meeting. Use ISO 8601 dates; note that Teams meetings require a work or school account.

Instructions

Create a calendar event with optional attendees, recurrence, and Teams online meeting.

Example: outlook_create_event(subject="Q3 review", start="2026-08-15T14:00:00Z", end="2026-08-15T15:00:00Z", attendees=["alice@acme.com"]) is_online is accepted but has no effect on personal accounts — Graph silently ignores isOnlineMeeting for consumer mailboxes (it returns isOnlineMeeting: False, onlineMeetingProvider: "unknown"). Teams meetings require a work/school account. start/end are ISO 8601. Passing recurrence creates a series, not a single event. It takes either a shorthand — "daily", "weekdays", "weekly", "monthly", "yearly", all anchored on start and open-ended — or a full Microsoft Graph recurrence object for anything else, e.g. every other Mon+Fri for 10 occurrences: {"pattern": {"type": "weekly", "interval": 2, "daysOfWeek": ["monday", "friday"]}, "range": {"type": "numbered", "numberOfOccurrences": 10}} range.startDate defaults to the event's start date. Prefer a bounded range ("endDate"/"numbered") when the event has attendees — a "noEnd" series invites them to every future occurrence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
bodyNo
startYes
subjectYes
locationNo
attendeesNo
is_onlineNo
is_all_dayNo
recurrenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.19.0
    • changedInput schema / properties / recurrence / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv1.11.0

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses significant behavioral details: is_online is silently ignored for personal accounts (returning false), recurrence creates a series rather than a single event, and range.startDate defaults to the event start. These go beyond the annotations (readOnlyHint false, destructiveHint false) and help set expectations for the tool's side effects.

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?

The description is detailed but well-organized: it leads with the main purpose, includes an example, then covers caveats and complex recurrence syntax with a concrete JSON example. Every sentence adds value — no fluff or repetition. The structure is logical, from basic usage to advanced edge cases.

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

Completeness5/5

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

For a create tool with optional complex recurrence, the description covers the essential edge cases: personal vs. work/school accounts for Teams, recurrence series behavior, and the importance of bounding series with attendees. It also clarifies date formats and defaults. No output schema exists, so return format isn't expected. The description is complete enough to call the tool correctly without additional context.

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?

The schema has zero parameter descriptions (0% coverage), but the description explains the non-obvious parameters: start/end are ISO 8601, recurrence accepts a shorthand or full Graph object, and is_online is a no-op on personal accounts. It also clarifies attendees in context of recurrence. Self-explanatory parameters like subject, location, body, and is_all_day are left to inference, which is acceptable given their obviousness.

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 creates a calendar event and lists optional features (attendees, recurrence, Teams meeting). The verb 'create' and resource 'calendar event' are specific, and the example further clarifies the action. This distinguishes it from siblings like outlook_update_event, outlook_delete_event, and outlook_list_events.

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

Usage Guidelines4/5

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

The description provides practical guidance, such as warning that is_online has no effect on personal accounts and that recurrence creates a series. It also recommends bounded ranges when attendees are present. However, it does not explicitly contrast with alternatives (e.g., 'use this for new events, not for updates'), though the tool name and purpose make that clear. Lacks an explicit when/when-not statement but gives useful caveats.

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