Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete stack

nextcloud_delete_stack
DestructiveIdempotent

Deletes a specified stack and all its cards from a Nextcloud Deck board using board and stack IDs. Use confirm for this destructive operation when the client cannot prompt.

Instructions

Delete one stack and its cards.

DELETE /index.php/apps/deck/api/v1.0/boards/{board_id}/stacks/{stack_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": {
      "board_id": "<board_id>",
      "stack_id": "<stack_id>"
    },
    "name": "nextcloud_delete_stack"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds real information beyond them: the deletion cascades to the stack's cards. It still omits irreversibility, permission requirements, and behavior when the stack does not exist.

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?

The behavioral statement is front-loaded and wastes no words. The appended raw HTTP route (DELETE /index.php/apps/deck/api/v1.0/...) adds little for an agent choosing and calling the tool, so it slightly dilutes an otherwise tight definition.

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, cascading delete with no output schema and two undocumented required identifiers, the description should say more — whether deletion is permanent, what error signals look like, and whether cards can be recovered. It covers the core effect but leaves an agent under-informed for a high-consequence operation.

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 only 33%: confirm is documented in the schema while board_id and stack_id are bare integers. The description adds no meaning to those identifiers (format, relationship between board and stack, or validity requirements), so the coverage gap is left unaddressed.

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?

"Delete one stack and its cards" gives a specific verb and resource and discloses the cascading scope, which distinguishes it from nextcloud_delete_card and nextcloud_delete_board. It does not explicitly name those siblings as alternatives, so it stops short of a 5.

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?

Nothing states when to use this tool versus deleting individual cards, deleting the parent board, or moving cards first. No preconditions (e.g., that the stack must belong to the given board) or recovery options are mentioned.

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