Skip to main content
Glama

List calendars

nextcloud_list_calendars
Read-onlyIdempotent

List all calendars in a Nextcloud account and show which components, such as events or tasks, each calendar contains.

Instructions

List the account's calendars and the components (VEVENT, VTODO) each holds.

PROPFIND /remote.php/dav/calendars/{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": "nextcloud_list_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful context that results include per-calendar component capabilities and discloses the underlying PROPFIND endpoint, but says nothing about output shape, pagination, or whether events themselves are returned.

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?

Two short lines with the core purpose front-loaded and no filler. The raw PROPFIND path is implementation detail that earns only marginal place, but it does not obstruct the main statement.

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?

With zero parameters, rich annotations, and no output schema, the description covers the essentials. It stops short of clarifying what the response actually contains (calendar names, colors, component flags vs. events), which is the main ambiguity an agent would face when choosing between this and nextcloud_list_events.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of the {user} path segment could confuse an agent into thinking a user argument exists, but it is presented as endpoint documentation rather than a 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?

States a specific verb and resource ('List the account's calendars') and adds what each entry contains (VEVENT/VTODO component types). An agent can distinguish it from nextcloud_list_events, though the description never names that sibling explicitly.

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?

There is no guidance on when to call this versus alternatives such as nextcloud_list_events, nextcloud_get_calendar_object, or nextcloud_create_calendar. Usage is only implied by the verb 'List'; an agent must infer that this is a discovery step before fetching events.

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