Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_list_events

Read-only

Lists Outlook calendar events in a date range, expanding recurring instances. Supports concise view for daily scans and cursor-based pagination.

Instructions

List calendar events in a date range (expands recurring instances).

Use for one-shot queries; use outlook_list_events_delta for polling/recurring agents.

Pass concise=True for day-at-a-glance scans: drops organizer, response_status, type and show_as; adds is_organizer and attendees_count; spells is_online as is_online_meeting.

calendar: a display name or an ID from outlook_list_calendars; omit for the default calendar. A cursor continues the listing it came from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
afterNo
countNo
beforeNo
cursorNo
conciseNo
calendarNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.22.1
    • addedInput schema / properties / calendar
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Calendar"
+}
  2. First observedv1.11.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true by disclosing that recurring instances are expanded, the exact field-level effects of concise=True (drops organizer/response_status/type/show_as, adds is_organizer/attendees_count, renames is_online), and that a cursor only continues the listing it came from.

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?

Front-loaded with purpose and the sibling rule, then tight, information-dense clauses. No filler sentences; every line adds an actionable fact.

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

Completeness4/5

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

No output schema exists, so the concise-mode field mapping usefully substitutes for describing the return shape, and recurring expansion plus cursor semantics are covered. However, pagination/count limits and the date-parameter formats are unaddressed, leaving how the range is actually computed ambiguous.

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?

With 0% schema description coverage, the description carries the burden and does well for the non-obvious params: calendar (display name or ID from outlook_list_calendars, omit for default), concise (full field mapping), and cursor (continuation semantics). It leaves days/after/before/count unexplained, including their formats and how they interact, which is the tool's central range-selection logic.

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+resource+scope: 'List calendar events in a date range (expands recurring instances).' It also explicitly names the sibling it is not (outlook_list_events_delta), so an agent can distinguish it without opening either schema.

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?

Explicit routing rule: 'Use for one-shot queries; use outlook_list_events_delta for polling/recurring agents.' It adds a second conditional for concise mode ('day-at-a-glance scans') and clarifies cursor reuse, covering when-to-use and which alternative to pick.

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