Skip to main content
Glama

List Calendar Events in a Date Range

list_calendar_view
Read-only

List calendar event instances between two dates, expanding recurring series into individual occurrences. Use it to answer questions like what's on my calendar this week.

Instructions

List event instances on the calendar between start_date_time and end_date_time. Expands recurring series into individual occurrences (unlike list_events which returns series masters). Use this for 'what's on my calendar this week'.

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_date_time": "<start_date_time>",
      "end_date_time": "<end_date_time>"
    },
    "name": "list_calendar_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMax events to return (default: 50)
time_zoneNoShow times in this zone: an IANA name (America/New_York) or a Windows one (Eastern Standard Time). Default: UTC. Pass the user's own zone to read times as they would.
calendar_idNoID of the calendar to use, from list_calendars. Omit for your default calendar.
end_date_timeYesWindow end (ISO 8601, e.g. 2026-05-29T00:00:00Z)
start_date_timeYesWindow start (ISO 8601, e.g. 2026-05-22T00:00:00Z)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds a genuinely useful behavioral fact beyond the annotations: recurring series are expanded into individual occurrences rather than returned as masters. It says nothing about cancelled/declined instances, result ordering, or what the truncated list looks like, which are the remaining behavioral gaps.

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?

Three short sentences, front-loaded with the operation and window, then the differentiating recurrence behavior, then a usage example. Nothing is padded, though the quoted example sentence is a convenience rather than load-bearing 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?

With five parameters all fully described in the schema, readOnlyHint covering safety, and the recurrence-expansion semantics spelled out, an agent has what it needs to call this correctly. There is no output schema, so the lack of any statement about return shape or truncation behavior is a minor residual gap rather than a blocker.

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 100% and the schema already documents top, time_zone, calendar_id, and the ISO 8601 formats. The description merely names start_date_time and end_date_time as the window bounds, adding no syntax, timezone, or defaulting nuance beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb ('List'), resource ('event instances on the calendar'), and an explicit window bounded by start_date_time and end_date_time. It also names the sibling it differs from ('unlike list_events which returns series masters'), so an agent can distinguish the two without opening either schema.

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?

Gives both the selecting condition (recurring series expanded into occurrences) and a concrete natural-language trigger ('what's on my calendar this week'). The alternative, list_events, is named with the reason to prefer this tool over it.

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

Deploy Server

Other Tools