Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete calendar

nextcloud_delete_calendar
DestructiveIdempotent

Deletes a specified Nextcloud calendar and all its contents by calendar URL, moving everything to the calendar trash.

Instructions

Delete one calendar and everything in it (it moves to the calendar trash).

DELETE /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": {
      "calendar_url": "<calendar_url>"
    },
    "name": "nextcloud_delete_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
calendar_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds genuinely new context by revealing the operation is recoverable ("moves to the calendar trash"), which materially softens the destructive hint, and it names the underlying DAV endpoint.

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?

Two compact sentences with the consequence front-loaded ahead of the technical endpoint line. Nothing is redundant, and the trash/recoverability detail is placed where it will be read.

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

Completeness4/5

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

For a destructive two-parameter delete with no output schema, the definition covers consequence, reversibility, and endpoint. It could have noted the restore path (nextcloud_restore_trash_item / list_trash) and behavior for a nonexistent calendar, but the essentials are present.

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 coverage is 50%: the confirm parameter is well documented in the schema, but calendar_url has no description. The URL template in the description partially compensates by showing the expected {user}/{slug} shape, though it does not clarify whether calendar_url is a path, slug, or full URL.

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 (Delete) and resource (one calendar) plus the blast radius ("everything in it"), which implicitly separates it from nextcloud_delete_calendar_object. It stops short of naming that sibling directly, so an agent must infer the distinction.

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 by the scope wording — whole-calendar deletion versus single-object deletion — but there is no explicit when-to-use/when-not guidance, no pointer to nextcloud_delete_calendar_object as the narrower alternative, and no note that the confirm flag is only needed when no interactive prompt exists.

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