Skip to main content
Glama

List events

nextcloud_list_events
Read-onlyIdempotent

Lists events from a specified Nextcloud calendar, optionally filtered by an ISO time range, to retrieve scheduled items for a given period.

Instructions

List the events of one calendar, optionally within an ISO time range.

REPORT /remote.php/dav/calendars/{user}/{calendar}

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": {
      "calendar_url": "<calendar_url>"
    },
    "name": "nextcloud_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
calendar_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • addedInput schema / properties / end
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / start
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  2. First observedv2.3.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior is covered. The description adds the DAV REPORT endpoint and optional ISO time range, but omits permissions, pagination, and return behavior. It adds some useful context beyond annotations but not rich behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the main purpose in the first sentence. The second sentence, a raw DAV REPORT path, is terse and somewhat jargon-heavy without explanation, but it does not bloat the definition.

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?

For a simple read-only list tool with annotations covering safety, this is close to adequate. However, with no output schema, the description should ideally mention return shape or pagination behavior, and it leaves the required calendar_url parameter underspecified.

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

Parameters2/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 compensate for all three parameters. It only vaguely indicates 'one calendar' and an 'ISO time range'; it does not explain the required calendar_url format, whether start/end are inclusive, timezone expectations, or how the path placeholders {user}/{calendar} relate to the calendar_url parameter.

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 states a specific verb and resource: 'List the events of one calendar'. It also clarifies the optional ISO time-range scope, which helps distinguish it from broader calendar-listing tools. However, it does not explicitly differentiate itself from siblings such as nextcloud_list_calendars or nextcloud_get_calendar_object.

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?

Usage is implied: use this when you need events from a single calendar, optionally filtered by time. There is no explicit guidance on when not to use it, no mention of listing calendars first to obtain the required calendar_url, and no pointer to create_event/update_event alternatives.

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