Skip to main content
Glama
littlebearapps

Outlook Assistant

by littlebearapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Calendar Events

list-events
Read-onlyIdempotent

Retrieve calendar events for the signed-in user, defaulting to upcoming ones. Filter by start time or subject to find past, current, or named events.

Instructions

List calendar events for the signed-in user (read-only). By default returns upcoming events (start ≥ now). Optional startAfter, startBefore and subject filters find past, current or specifically-named events; supplying any of them replaces the default "now" lower bound and the filters are AND-ed together. Results are oldest first, except when the search only looks backwards (startBefore without startAfter, or subject alone), where they are newest first. Each event shows its subject, location, start/end, a body preview and its id. Use count (default 10, max 100) to control page size. Each start/end is returned as a canonical UTC ISO-8601 instant (e.g. 2026-04-02T22:00:00.000Z) followed by a labelled local rendering in the configured display timezone (default Australia/Melbourne; override with OUTLOOK_DEFAULT_TIMEZONE) — the UTC value is authoritative, so consumers never have to guess the zone.

Input Schema

NameRequiredDescriptionDefault
countNoNumber of events to retrieve (default: 10, max: 100)
subjectNoOptional substring (max 255 characters) to match against the event subject, case-insensitive (Graph `contains()`). Useful for finding past or current events by name; on its own, results are newest first.
startAfterNoOptional ISO 8601 datetime with `Z` or a ±hh:mm offset (required). Only return events whose start is on or after this time. Replaces the default "now" lower bound when supplied. Example: "2026-01-01T00:00:00Z" or "2026-01-01T09:00:00+10:00".
startBeforeNoOptional ISO 8601 datetime with `Z` or a ±hh:mm offset (required). Only return events whose start is strictly before this time. Combine with `startAfter` to bound a window; on its own, results are newest first. Example: "2026-02-01T00:00:00Z".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.14.1
    • changedInput schema / properties / count / description
      Previous value: -"Number of events to retrieve (default: 10, max: 50)"New value: +"Number of events to retrieve (default: 10, max: 100)"
    • addedInput schema / properties / startAfter
      Added value: +{
+  "description": "Optional ISO 8601 datetime with `Z` or a ±hh:mm offset (required). Only return events whose start is on or after this time. Replaces the default \"now\" lower bound when supplied. Example: \"2026-01-01T00:00:00Z\" or \"2026-01-01T09:00:00+10:00\".",
+  "format": "date-time",
+  "type": "string"
+}
    • addedInput schema / properties / startBefore
      Added value: +{
+  "description": "Optional ISO 8601 datetime with `Z` or a ±hh:mm offset (required). Only return events whose start is strictly before this time. Combine with `startAfter` to bound a window; on its own, results are newest first. Example: \"2026-02-01T00:00:00Z\".",
+  "format": "date-time",
+  "type": "string"
+}
    • addedInput schema / properties / subject
      Added value: +{
+  "description": "Optional substring (max 255 characters) to match against the event subject, case-insensitive (Graph `contains()`). Useful for finding past or current events by name; on its own, results are newest first.",
+  "maxLength": 255,
+  "type": "string"
+}
  2. Changed1 schema field changedv3.7.4
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv3.4.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantial extra behavior: the default 'now' lower bound, the sort-order inversion when searching backwards, page-size limits, and the authoritative-UTC-plus-local-rendering time format.

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?

Front-loads purpose, scope, and default behavior, then layers filter and timezone details. Dense and mostly waste-free, though the timezone rendering sentence is longer than strictly necessary.

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 no output schema, the description fully covers the returned fields (subject, location, start/end, body preview, id) and their format, so an agent knows what to expect without one.

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 each parameter is already documented. The description nonetheless adds interaction semantics the schema lacks: that supplying any filter replaces the default lower bound, that filters are AND-ed, and how each affects ordering.

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 (list calendar events) scoped to the signed-in user and explicitly read-only, which cleanly separates it from write-oriented siblings like create-event and manage-event.

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?

Clearly explains the default behavior (upcoming events from now) and when the optional filters change that default, including the AND-ed combination and sort-order effects. It does not name or contrast against sibling tools, so it stops short of full when/when-not/alternatives guidance.

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