Skip to main content
Glama
Sign In
calendar-mcp

calendar-mcp

by p-l-ta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_events

Read-only

List calendar events within a specified date range, expanding recurring events for complete visibility. Query Calendar.app's OccurrenceCache and get events sorted by start time.

Instructions

List calendar events within a date range. Queries the Calendar.app SQLite database via OccurrenceCache, which correctly expands recurring event instances rather than just listing master events. Returns events sorted by start time.

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": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesISO 8601 end of the window (exclusive). Events whose occurrence starts before this time are included.
limitNo
startYesISO 8601 start of the window, e.g. '2026-05-01T00:00:00' or '2026-05-01'. Events whose occurrence starts on or after this time are included.
calendar_uuidNoRestrict results to a single calendar. Pass a UUID from list_calendars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false. Description adds that the tool queries the OccurrenceCache, expands recurring instances, and sorts by start time, which are useful behavioral details beyond what annotations provide.

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?

Three short sentences, no redundancy. Purpose stated first, then technical detail, then output ordering. Every sentence earns its place.

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?

Covers main behavior, expansion, ordering. No output schema exists, so return format is not described, but the description gives enough context for a list operation. Could mention pagination or default limit behavior more explicitly.

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 coverage is 75% (3 of 4 params described). Description adds clarification: start and end are ISO 8601, end is exclusive, calendar_uuid should come from list_calendars. This adds practical meaning beyond the schema alone.

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?

Clearly states the verb 'List' and resource 'calendar events within a date range'. Differentiates from siblings like list_calendars (lists calendars) and search_events (likely searches by text).

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?

Implied usage: for listing events in a date range. No explicit guidance on when not to use or alternatives, but context from description and sibling names provides some differentiation.

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