Calendar MCP Server

list_events

Retrieve calendar events within a specified date range, including expanded recurring events, to view scheduled activities and appointments.

Instructions

List calendar events within a specific date range, expanding recurring events.

Args:
    start_date: Start of the range (ISO format, e.g., '2023-01-01')
    end_date: End of the range (ISO format)

Returns:
    List of events falling within the range.

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": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "list_events"
  }
}

Input Schema

Name	Required	Description	Default
`start_date`	Yes
`end_date`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a read operation (list) and specifies date range filtering and recurring event expansion. However, it doesn't mention pagination behavior, rate limits, authentication requirements, or error conditions that would be helpful for an agent.

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 perfectly structured and concise - purpose statement first, followed by Args and Returns sections. Every sentence earns its place with no wasted words. The information is front-loaded with the core functionality stated immediately.

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?

Given the tool's moderate complexity (date range filtering with recurring event expansion) and the presence of an output schema, the description provides good coverage. It explains what the tool does, documents parameters, and mentions the return type. However, it could benefit from more behavioral context given the lack of annotations.

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?

With 0% schema description coverage, the description compensates well by providing format examples (ISO format) and clarifying the purpose of both parameters. The Args section explicitly documents both required parameters with format guidance, adding significant value beyond the bare schema.

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 verb ('List') and resource ('calendar events'), specifies the scope ('within a specific date range'), and distinguishes from sibling tool 'search_events' by mentioning the expansion of recurring events. This provides specific differentiation from alternatives.

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?

The description provides clear context about when to use this tool ('within a specific date range, expanding recurring events'), but doesn't explicitly state when NOT to use it or provide detailed alternatives. The existence of 'search_events' as a sibling tool is noted but not explained, leaving some ambiguity about tool selection.

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

Deploy Server