nc-mcp-server

get_events

Read-onlyIdempotent

Retrieve calendar events within an optional time range, including recurring instances, with pagination and calendar selection.

Instructions

Get events from a calendar, optionally filtered by time range.

Without start/end, returns all events in the calendar. With start and end, returns only events overlapping that range (including recurring event instances).

Args: calendar_id: Calendar identifier (default "personal"). Use list_calendars to find IDs. start: Optional range start in ISO 8601 UTC format: "2026-04-01T00:00:00Z". Required if end is provided. end: Optional range end in ISO 8601 UTC format: "2026-04-30T23:59:59Z". Required if start is provided. limit: Maximum number of events to return (1-500, default 50). offset: Number of events to skip for pagination (default 0).

Returns: JSON with "data" (list of event objects) and "pagination" (count, offset, limit, has_more).

Input Schema

TableJSON Schema

Name	Required	Default
`end`	No
`limit`	No
`start`	No
`offset`	No
`calendar_id`	No	personal

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds meaningful context: the overlapping time-range semantics, inclusion of recurring event instances, and the pagination response structure, which go beyond the annotation hints.

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 well-structured with a one-sentence purpose, clear behavior notes, bullet-style args, and a return format section. Every sentence adds value with no redundancy or filler.

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?

Given the five parameters Thorough documentation, an output schema existence, and the read-only nature already flagged by annotations, the description is sufficient for an agent to invoke the tool correctly. It covers parameter formats, defaults, requiredness dependencies, and response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 fully explain parameters, and it does. It specifies ISO 8601 format for start/end, the dependency between them, valid limit range (1-500), default values, and how to discover calendar_id via list_calendars.

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?

The description clearly states the tool retrieves events from a calendar with optional time filtering. It uses a specific verb and resource, and the plural 'events' distinguishes it from the sibling get_event tool, though it does not explicitly call out that sibling.

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 description explains the behavior with and without start/end parameters, giving implicit usage context. It mentions using list_calendars to find calendar IDs, but it does not explicitly say when to prefer this tool over alternatives such as get_event or list_calendars.

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

Deploy Server