Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

list_calendar_events

Read-onlyIdempotent

Lists calendar event occurrences in a date range, expanding recurring events so you can review scheduled meetings by account, calendar, and timezone.

Instructions

List calendar event occurrences in a date range (recurring events are expanded).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "<start>"
    },
    "name": "list_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd, inclusive day or ISO 8601. Default: start + 7 days
limitNo
startYesStart, YYYY-MM-DD or ISO 8601 (local time if no offset)
accountNo
calendarNoCalendar name contains this text
timezoneNoIANA timezone for input and output times (default: this Mac's zone)
include_cancelledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact — recurring events are expanded into occurrences — but says nothing about ordering, the 200 default / 500 max limit, or that cancelled events are excluded by default.

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 front-loaded sentence with zero filler and the key behavior in parentheses. It is efficient, though its brevity is part of why other dimensions are thin.

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

Completeness2/5

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

For a 7-parameter, no-output-schema tool, the description omits the default range (start + 7 days), the result cap, the timezone handling, and the cancelled-event default. What remains is correct but leaves an agent to open the schema to call it reliably.

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 57%, so roughly half the parameters (limit, account, include_cancelled) are undocumented, and the description adds no parameter meaning beyond reiterating the date range. The recurring-expansion note is about output shape rather than any input, so it does not compensate for the coverage gap.

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 (List) and resource (calendar event occurrences) plus the scoping qualifier 'in a date range' and the notable behavior that recurring events are expanded. It does not distinguish itself from siblings such as search_calendar or calendar_freebusy, so it stops short of a 5.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. An agent must infer that this is for browsing a bounded window rather than searching by text (search_calendar) or checking availability (calendar_freebusy).

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