Skip to main content
Glama

get-calendar-view

Read-only

Retrieve calendar events within a specified date range, including recurring instances, from your Microsoft 365 calendar. Define start and end times in ISO 8601 format to view scheduled appointments and meetings.

Instructions

Get the occurrences, exceptions, and single instances of events in a calendar view defined by a time range, from the user's default calendar, or from some other calendar of the user.

šŸ’” TIP: Returns expanded recurring event instances (not just seriesMaster) within a date range for the default calendar. Requires startDateTime and endDateTime query parameters in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Use get-specific-calendar-view if you need a non-default calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateTimeYesThe start date and time of the time range, represented in ISO 8601 format. For example, 2019-11-08T19:00:00-08:00
endDateTimeYesThe end date and time of the time range, represented in ISO 8601 format. For example, 2019-11-08T20:00:00-08:00
topNoShow only the first n items
skipNoSkip the first n items
searchNoSearch items by search phrases
filterNoFilter items by property values
countNoInclude count of items
orderbyNoOrder items by property values
selectNoSelect properties to be returned
expandNoExpand related entities
fetchAllPagesNoAutomatically fetch all pages of results
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
timezoneNoIANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC.
expandExtendedPropertiesNoWhen true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false. Description adds crucial behavioral context not in annotations: 'Returns expanded recurring event instances (not just seriesMaster)' and clarifies timezone handling via the timezone parameter description in schema.

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-loaded with core purpose, followed by šŸ’” TIP section containing usage guidance. Slightly redundant phrasing 'default calendar, or from some other calendar' could be tighter, but overall efficient with no wasted sentences.

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 15 parameters, 100% schema coverage, and annotations present, description sufficiently covers behavioral nuances (event expansion) and sibling routing without needing to document return values (no output schema provided).

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 has 100% coverage (baseline 3). Description adds value by emphasizing 'Requires startDateTime and endDateTime' and providing additional ISO 8601 example '2024-01-01T00:00:00Z', reinforcing the format requirement beyond schema descriptions.

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?

Description uses specific verb 'Get' with clear resource 'occurrences, exceptions, and single instances of events in a calendar view'. The tip explicitly distinguishes from sibling 'get-specific-calendar-view' by stating when to use each (default vs non-default calendar), eliminating ambiguity.

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?

Explicitly states alternative: 'Use get-specific-calendar-view if you need a non-default calendar'. Also clarifies this returns 'expanded recurring event instances (not just seriesMaster)', guiding when to use this over list-calendar-events.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alfredo-ia/ms-365-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server