Skip to main content
Glama
Sign In
sam2kb

m365-mcp

by sam2kb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

m365_calendar_list

Read-onlyIdempotent

List Microsoft 365 calendar events for a specified or default calendar, supplying start and end datetimes to expand recurring occurrences within that range.

Instructions

List calendar events; supply both dates to expand recurring events within a range

Input Schema

NameRequiredDescriptionDefault
topNoMax events
calendarIdNoOptional calendar ID; omit to preserve the default /me event scope
endDateTimeNoEnd datetime (ISO 8601)
startDateTimeNoStart datetime (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • addedInput schema / properties / calendarId
      Added value: +{
+  "description": "Optional calendar ID; omit to preserve the default /me event scope",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / top / maximum
      Added value: +500
    • addedInput schema / properties / top / minimum
      Added value: +1
    • changedInput schema / properties / top / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.0.7

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds one genuinely non-obvious trait — recurring events are only expanded when both dates are supplied — but stops short of saying what the default range is or what occurs with partial date input, and says nothing about result volume or pagination despite a 'top' cap.

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

Conciseness4/5

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

A single short sentence with the primary action front-loaded and zero padding. It is efficient, though the second clause is slightly compressed to the point of ambiguity about partial date input.

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?

Hmm—reconsidering: the tool is a list operation with no required parameters, no output schema, and no nested objects. The description leaves unclear what happens by default when no dates are given, which for a zero-required-param list tool is the most likely call pattern. Given the absence of an output schema and the breadth of calendar siblings, this is a meaningful omission.

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 four parameters are already documented, including the calendarId default-scope note and ISO 8601 formatting. The description adds no format or syntax detail beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('List calendar events'), so the operation is unambiguous. However it does not distinguish itself from siblings like m365_calendar_today, m365_calendar_week, m365_calendar_get, or m365_calendar_availability, leaving the agent to infer which listing variant to pick.

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?

The phrase 'supply both dates to expand recurring events within a range' is a real usage rule for the date parameters. But there is no guidance on when to choose this over the today/week/get/availability siblings, and no statement about what happens when dates are omitted.

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