copilot-outlook-connector

Overview Schema Source Related Servers Discussions Admin

calendar_list_events

Read-only

List calendar events within a specified time range for a given calendar and account, returning occurrences, exceptions, and single events with pagination limits.

Instructions

Read bounded UTC calendarView occurrences, exceptions and single events. Follows all safe pages up to limits; complete=false is never a complete/free result.

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": {
      "accountId": "<accountId>",
      "calendarId": "<calendarId>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "calendar_list_events"
  }
}

Input Schema

Name	Required	Description
`end`	Yes
`limit`	No
`start`	Yes
`accountId`	Yes
`calendarId`	Yes	Exact calendar ID from discovery, or "default" to resolve /me/calendar.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description goes beyond the readOnlyHint annotation by explaining pagination behavior and the semantics of complete=false. It accurately reflects the read-only nature and does not contradict any annotations.

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?

The description is very concise and contains no irrelevant or redundant content. The two sentences deliver the key semantic points without unnecessary detail.

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?

Given the tool's moderate complexity and lack of an output schema, the description covers important behavioral context such as pagination and boundedness. It does not describe response fields or error cases, but those are not strictly required for basic invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only calendarId has a schema description; accountId, start, end, and limit receive no explicit explanation in the description. The description implies UTC and boundedness but does not clarify parameter roles or format expectations beyond the schema's regex and bounds.

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 clearly identifies the action as reading calendarView data and specifies the scope (bounded UTC occurrences, exceptions, and single events). It is distinguishable from sibling tools like calendar_search_events and calendar_list_instances, though the term 'calendarView' could be slightly more explicit.

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 description gives useful pagination guidance ('Follows all safe pages up to limits') and clarifies the meaning of complete=false, which helps callers understand result completeness. However, it does not explicitly state when to prefer this tool over alternatives such as calendar_search_events or calendar_list_instances.

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