Local MCP

Microsoft 365 Create Event

m365_create_event

Creates an event in the connected Microsoft 365 / Outlook calendar. If attendees is set, Microsoft 365 emails each of them a meeting invitation as soon as the event is created: creating with attendees IS sending invitations, so check the list with the user first. Times are read in timezone, which defaults to UTC — pass the user's timezone or the event lands at the wrong hour. Uses the primary calendar unless calendar names another. Called without confirm it returns a preview of every field and touches nothing; pass confirm=true to create. Returns the event id. For the Mac's Calendar app use create_calendar_event instead.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	Yes	End time in ISO 8601, e.g. '2026-05-20T11:00:00'
`body`	No	Event description (optional)
`start`	Yes	Start time in ISO 8601, e.g. '2026-05-20T10:00:00'
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
`confirm`	No	Must be true to create the event
`subject`	Yes	Event title
`calendar`	No	Calendar name to create the event in — partial, case-insensitive match (optional). Omit to use the primary calendar.
`location`	No	Location (optional)
`timezone`	No	IANA timezone, e.g. 'America/New_York' (default: UTC)
`attendees`	No	Comma-separated email addresses to invite (optional)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`ok`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}

addedOutput schema / properties / account

Added value: +{
+  "description": "The email (UPN) of the Microsoft 365 account this call used.",
+  "type": "string"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "Must be true to create the event",
+  "type": "boolean"
+}

Changed1 schema field changedSep 29, 2026

removedInput schema / properties / confirm

Removed value: -{
-  "description": "Must be true to create the event",
-  "type": "boolean"
-}

Changed1 schema field changedSep 21, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "Must be true to create the event",
+  "type": "boolean"
+}

First observedJun 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, openWorld=true), but the description adds substantial side-effect context the annotations cannot: setting attendees immediately emails invitations, timezone defaults to UTC or the event lands at the wrong hour, and confirm=false is a no-op preview. This is exactly the behavioral disclosure that matters for a mutation tool.

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?

Dense but front-loaded: purpose first, then the invitation side-effect, then the timezone hazard, then the confirm flow, then the sibling routing. Every sentence carries actionable information with no filler.

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?

With an output schema present, return values need not be detailed, yet it still notes 'Returns the event id'. Combined with 100% param coverage and rich behavioral context, an agent has everything needed to invoke this correctly and safely.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the timezone default of UTC and its consequence, the primary-calendar default for 'calendar', and that confirm=false returns a full preview rather than failing. Marginal gain over the schema, hence a 4 rather than 5.

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 ('Creates an event in the connected Microsoft 365 / Outlook calendar') and explicitly names the sibling it is not ('For the Mac's Calendar app use create_calendar_event instead'), letting an agent route correctly without opening schemas.

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?

Gives explicit when-to-use routing to create_calendar_event, warns to check the attendee list with the user before inviting, and explains the confirm preview flow. The conditions that select the tool versus its alternative are stated, not inferred.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.