Skip to main content
Glama
Sign In
synology-office-mcp

synology-office-mcp

by vocweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

calendar_list_calendars

List all Synology Calendar calendars accessible to the authenticated user, enabling streamlined calendar management.

Instructions

List all Synology Calendar calendars accessible to the authenticated user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendar_list_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'list' implies a read operation, no additional behavioral traits (e.g., pagination, rate limits, or safety guarantees) are disclosed beyond the basic purpose.

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 a single sentence with no extraneous information. It is front-loaded, directly stating the action and scope, making it efficient and easy to parse.

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 the low complexity (no parameters, no output schema), the description is minimally viable but lacks details like return format or relation to sibling tools. It is adequate for a simple list operation but not enriched.

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 zero parameters, schema coverage is 100% (vacuously). The description adds no parameter-specific meaning, but the baseline is 4 per guidelines for zero parameters. No additional value is needed.

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?

Description clearly states 'List all Synology Calendar calendars accessible to the authenticated user,' using a specific verb ('List') and resource ('calendars'). It distinguishes from sibling tools like 'calendar_create_calendar' and 'calendar_list_events' by specifying the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives is provided. The description does not mention prerequisites, context, or scenarios for exclusion. It simply states what it does, leaving the agent without usage strategy.

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