Local MCP

Microsoft 365 List Events

m365_list_events

Read-only

List upcoming calendar events from your Microsoft 365 / Outlook calendar.

Input Schema

Name	Required	Description
`days`	No	Number of days to look, counted from start (default 7, max 30)
`limit`	No	Max events to return (default 20, max 50)
`start`	No	Where the window begins: an ISO 8601 date (local midnight, e.g. '2026-10-24' for the whole local day with days=1) or date-time. Default: now.
`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.
`calendar`	No	Calendar name to filter by — partial, case-insensitive match (optional). Omit to use the primary calendar.

Output Schema

Name	Required	Description
`days`	No
`count`	No
`events`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`calendar`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / days / description

Previous value: -"Number of days ahead to look (default 7, max 30)"New value: +"Number of days to look, counted from start (default 7, max 30)"

addedInput schema / properties / start

Added value: +{
+  "description": "Where the window begins: an ISO 8601 date (local midnight, e.g. '2026-10-24' for the whole local day with days=1) or date-time. Default: now.",
+  "type": "string"
+}

Changed2 schema fields changedOct 24, 2026
- addedInput schema / properties / days / maximum
```
Added value: +30
```
- addedInput schema / properties / limit / maximum
```
Added value: +50
```

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"
+}

First observedJun 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only 'upcoming', which hints at future-event filtering, but does not explain time window behavior, pagination, account defaults, or calendar selection nuances beyond what the schema provides.

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?

A single front-loaded sentence with zero wasted words. It is concise and immediately states the core action and source.

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

Completeness3/5

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

The tool has an output schema and fully documented parameters, so the description needn't explain return values or parameter details. However, it omits useful context such as how this differs from the generic 'list_calendar_events' sibling and any account/calendar selection behavior, leaving a moderate gap.

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%, so all five parameters are fully documented in the schema itself. The description adds no parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 description gives a specific verb ('List') and resource ('upcoming calendar events') and names the provider ('Microsoft 365 / Outlook calendar'). However, it does not explicitly distinguish this tool from the sibling 'list_calendar_events', leaving ambiguity about which calendar source is appropriate.

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?

The description offers no explicit guidance on when to use this tool versus alternatives like 'list_calendar_events' or 'm365_create_event'. It only implies usage through 'upcoming calendar events', with no exclusions or conditions.

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.