copilot-outlook-connector

Overview Schema Source Related Servers Discussions Admin

calendar_list_instances

Read-only

Retrieve exact occurrence and exception IDs from a recurring calendar series in a time window. Use these IDs with the series master for reliable occurrence actions instead of deriving from dates.

Instructions

Get exact occurrence/exception IDs from a verified seriesMaster in a bounded window. Use returned ID, master and originalStart for occurrence actions; never derive IDs from dates.

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>",
      "seriesMasterId": "<seriesMasterId>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "calendar_list_instances"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation by mentioning the requirement of a 'verified seriesMaster' and a 'bounded window.' It also alerts users not to derive IDs from dates, a valuable operational caveat. The read-only nature is already covered by 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 two short sentences, directly states the main purpose first, and includes a clear usage directive. It is concise and well-structured without unnecessary verbosity.

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?

The description adequately explains what the tool does and how to use the returned data, referencing key fields. It does not mention pagination, error cases, or the exact response list format, but for a read-only instance lookup, the provided information is sufficient for typical usage.

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?

The description clarifies start and end as defining a 'bounded window' and seriesMasterId as needing a 'verified seriesMaster.' It also references 'originalStart' in the response, which helps understand the return shape. However, accountId is not explained beyond its name, and calendarId's description in the schema is not reinforced.

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?

The description clearly states the tool's function with the verb 'Get' and specifies the resource: 'exact occurrence/exception IDs from a verified seriesMaster in a bounded window.' It also distinguishes this from general event listing by focusing on recurring series instances and explicitly mentions use for occurrence actions.

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?

It provides practical guidance on how to use the results ('Use returned ID, master and originalStart for occurrence actions') and warns against a common mistake ('never derive IDs from dates'). However, it does not explicitly compare to sibling tools like calendar_list_events, leaving the choice of this tool vs. alternatives somewhat implicit.

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