Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete group

nextcloud_delete_group
DestructiveIdempotent

Delete a Nextcloud group while keeping its members' accounts intact. Use it to remove obsolete groups without deleting user data.

Instructions

Delete one group (its members keep their accounts).

DELETE /ocs/v2.php/cloud/groups/{group_id}

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": {
      "group_id": "<group_id>"
    },
    "name": "nextcloud_delete_group"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds genuinely new behavior: member accounts survive the group deletion, i.e. the delete is non-cascading — the single most important thing an agent needs to know before calling this. It does not state reversibility or error behavior, hence not a 5.

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 substantive fact (members keep accounts) placed first, so it is front-loaded and waste-free. The raw endpoint path is of marginal value to an agent but is cheap and aids error interpretation.

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 destructive, one-required-parameter tool with no output schema and strong annotation coverage, the definition covers the essential blast radius. It omits the confirmation flow (whether the server will prompt, and what happens if 'confirm' is false), permission requirements, and behavior when the group does not exist.

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 itself, but 'group_id' has no description anywhere. The description only implies the identifier's role via the URL template '{group_id}', and it never mentions the confirmation parameter or when it is needed. Baseline 3 applies since the schema carries half the burden.

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 ('Delete one group') and disambiguates it from the sibling nextcloud_delete_user by noting that 'its members keep their accounts'. It is clear what the tool does, though it does not explicitly name a sibling alternative.

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 destructive verb and the group scope, but there is no explicit when-to-use guidance, no mention of prerequisites (admin rights), and no pointer to related tools like nextcloud_list_groups or nextcloud_delete_user for the contrasting case.

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