Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create calendar

nextcloud_create_calendar

Creates a Nextcloud calendar for events and, by default, tasks, using a display name and optional slug to organize schedules and to-dos.

Instructions

Create one calendar that holds events and, by default, tasks.

MKCALENDAR /remote.php/dav/calendars/{user}/{slug}

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": {
      "display_name": "<display_name>"
    },
    "name": "nextcloud_create_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
with_tasksNo
display_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation and network profile are known. The description adds useful context beyond that: the underlying MKCALENDAR/WebDAV endpoint and the fact that task support is enabled by default. It omits failure modes such as duplicate-slug conflicts and required permissions.

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: the core purpose is front-loaded in the first sentence, and the endpoint is appended as a compact technical reference. No filler, though the bare URL line is slightly cryptic without a label.

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?

This is a low-complexity, three-parameter creation tool with no output schema, so the description does not need to explain return values. It covers the resource and one default but leaves slug derivation and conflict behavior undocumented, which is the main gap an agent would hit when calling it.

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 carry the load, and it only partially does: 'by default, tasks' explains the with_tasks default but not what setting it to false does. The slug parameter, including what happens when it is null and how it relates to display_name, is left entirely unexplained.

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 uses a specific verb and resource ('Create one calendar') and clarifies scope by noting it holds events and, by default, tasks, which separates it from nextcloud_create_event. It does not explicitly name the sibling alternatives (create_event vs. create_calendar), so it stops short of full differentiation.

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 use this versus nextcloud_create_event or nextcloud_list_calendars, no mention of prerequisites such as authentication or required user context, and no stated behavior when a calendar with the same slug already exists. The 'by default, tasks' phrasing only weakly implies the with_tasks option.

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