synology-office-mcp

calendar_list_events

Retrieve Synology Calendar events within a specified date range. Supports filtering by calendar ID and setting a limit on the number of events returned.

Instructions

List Synology Calendar events within a date range. ISO 8601 dates without a timezone offset are interpreted as NAS local 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_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "calendar_list_events"
  }
}

Input Schema

Name	Required	Description
`calendar_id`	No	Filter by calendar ID. If omitted, returns events from all calendars.
`start_date`	Yes	Start of range in ISO 8601: 'YYYY-MM-DD' or 'YYYY-MM-DDTHH:mm:ss'. ISO without offset is interpreted as NAS local time.
`end_date`	Yes	End of range in ISO 8601: 'YYYY-MM-DD' or 'YYYY-MM-DDTHH:mm:ss'. ISO without offset is interpreted as NAS local time.
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0May 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses ISO 8601 timezone handling but omits other behaviors like pagination (limit parameter), result format, or error scenarios.

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?

Two sentences with clear front-loading: action first, then a single important caveat. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 4 parameters, the description covers purpose and date interpretation but lacks details on default limit, pagination, ordering, and response format, leaving gaps for an agent.

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 75%; the description adds no extra meaning beyond what the schema already provides for start_date/end_date (ISO interpretation). Calendar_id and limit lack additional context.

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 tool lists Synology Calendar events within a date range using a specific verb and resource. It distinguishes from sibling tools like calendar_create_event (creates) and calendar_list_calendars (lists calendars).

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 implies usage for listing events in a date range but provides no explicit when-to-use or when-not-to-use guidance, nor mentions alternatives like search tools.

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

Deploy Server