Skip to main content
Glama

calendar_events

Read-only

List Outlook calendar events between two ISO dates or date-times, including both endpoints, to retrieve scheduled items from Microsoft Graph.

Instructions

List calendar events between two ISO dates or date-times, e.g. start=2026-11-16, end=2026-11-23 (both days included). Dates and times without an offset, and the times shown, are in the server's time zone (see the server instructions).

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>",
      "end": "<end>"
    },
    "name": "calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
topNo
startYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds non-obvious behavior: offset-less inputs and returned times are interpreted in the server's time zone, with a pointer to the server instructions. The remaining gap is that neither the cap on results nor pagination behavior is disclosed.

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 sentence with the required-parameter example front-loaded and the time-zone caveat trailing; nothing is redundant. The embedded line break and parenthetical are slightly awkward but do not obscure the content.

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?

An output schema exists, so return values need not be described, and the time-zone and date-format semantics cover the trickiest part of calling this tool correctly. The one material omission relative to a 3-parameter listing tool is any statement about the result cap and how to retrieve more.

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 0%, so the description must carry parameter meaning — and it does explain 'start' and 'end' with an ISO example and the both-days-inclusive semantics. The third parameter, 'top' (default 50), is never mentioned, leaving one of three parameters entirely undocumented in both places.

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?

Names a specific verb and resource ('List calendar events') and defines the scope precisely as a range between two ISO dates or date-times, including the inclusivity rule ('both days included'). It does not need to differentiate from a calendar sibling since none exists, but it also never states what distinguishes it from generic listing tools.

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 bounded-range context implies when to call it (you need events in a window), and the inclusivity note is a genuine usage aid. However, there is no explicit when-not guidance, no mention of paging through results or of what to do if the window is large, which matters given the silent 'top' default of 50.

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