nextcloud-mcp

get_calendar_events

Retrieve calendar events from Nextcloud with optional start and end dates. Filter by date range to get events for a specific period.

Instructions

Retrieve calendar events from Nextcloud. Can specify date range.

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

Input Schema

Name	Required	Description
`limit`	No	Max events to return
`endDate`	No	End date YYYY-MM-DD (defaults to 30 days from start)
`startDate`	No	Start date YYYY-MM-DD (defaults to today)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'Retrieve' and 'Can specify date range,' but does not disclose read-only nature, return format, pagination, or any side effects. This is a significant gap for a tool with zero annotation support.

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 two short sentences with no redundant wording. It is extremely concise and every word serves a purpose, earning a high score for structure.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description is under-specified. It does not mention return value structure, sorting, or any caveats about calendar events. This leaves the agent with insufficient context to understand what the tool actually returns.

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 100%, so the baseline is 3. The description's mention of 'date range' adds no meaning beyond the schema's startDate and endDate descriptions. It does not compensate or provide additional parameter semantics.

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 'Retrieve calendar events from Nextcloud', using a specific verb and resource. It distinguishes from sibling tools like get_tasks and create_calendar_event by focusing on calendar events and the retrieval action.

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 retrieving calendar events but provides no explicit context on when to use this tool over alternatives, no exclusions, and no references to sibling tools. It is a generic action statement without guidance.

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