nc-mcp-server

delete_circle

DestructiveIdempotent

Delete a circle as its owner and remove all memberships. Optionally erase the linked team folder and every file in it by setting delete_team_folder to true.

Instructions

Delete a circle. Requires owner level. Removes all memberships.

Args: circle_id: String circle id. delete_team_folder: Deleting a circle also deletes its team folder (Nextcloud 35+ with the Team folders app) and every file in it, for all members, also when it is an older group folder an admin linked to the team. If the circle has one, the tool refuses unless this is true.

Returns: Confirmation with the deleted id, and deleted_team_folder (the folder's name) when a team folder goes with it. Circles finishes the deletion in the background within seconds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`circle_id`	Yes
`delete_team_folder`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0Oct 1, 2026

addedInput schema / properties / delete_team_folder

Added value: +{
+  "default": false,
+  "title": "Delete Team Folder",
+  "type": "boolean"
+}

First observedv0.7.0Sep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark it destructive and idempotent, and the description adds substantial context beyond that: owner-level auth requirement, removal of all memberships, cascading team-folder file deletion across all members, refusal semantics, and that deletion completes in the background within seconds. This is rich behavioral disclosure.

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?

Front-loaded with the core action and preconditions, and the Args/Returns structure is easy to scan. The team-folder paragraph is long and version-specific, but each detail is operationally relevant to avoiding accidental data loss.

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

Completeness5/5

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

For a destructive mutation with an output schema, the description covers auth requirements, cascade behavior, refusal conditions, and background timing. Nothing an agent needs to call it safely is missing.

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?

Schema coverage is 0%, so the description carries the burden. It fully explains delete_team_folder including the Nextcloud 35+/Team folders variant and the refusal when omitted, but circle_id is described only as 'String circle id,' which adds little over the schema title.

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 opening 'Delete a circle' states a specific verb and resource, then immediately qualifies scope with 'Requires owner level' and 'Removes all memberships.' An agent can distinguish this from siblings like leave_circle, delete_collective, or remove_circle_member without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the precondition ('Requires owner level') and a hard refusal condition when a team folder exists and delete_team_folder is not true, which is real when-to-use guidance. It does not explicitly contrast with leave_circle or remove_circle_member, so it stops short of full alternative routing.

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

Deploy Server