Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete board

nextcloud_delete_board
DestructiveIdempotent

Delete a Nextcloud Deck board by ID, with an optional confirmation flag for destructive actions. The board remains restorable for a limited time.

Instructions

Delete one board (Deck keeps it restorable for a while).

DELETE /index.php/apps/deck/api/v1.0/boards/{board_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>"
    },
    "name": "nextcloud_delete_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
board_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 and idempotentHint=true, so the safety profile is known. The description adds a genuinely non-obvious trait: the Deck backend keeps the board restorable for a while, i.e. this is a soft delete, which materially affects how an agent should warn the user. It does not explain the confirm parameter or permission requirements, keeping it from 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 compact lines with the core action front-loaded and no filler. The raw endpoint line is arguably noise for an LLM but is short and could aid API-aware agents, so it does not seriously hurt readability.

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, irreversibility-adjacent operation with no output schema, the description covers the crucial restorability fact but leaves out where board_id comes from, what confirm does when omitted, and what a successful response returns. Annotations carry the destructive flag, so the gap is not severe, but the definition is only minimally complete.

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 coverage is only 50%: confirm is documented inline, but board_id has no description at all. The description does not compensate, offering no indication that board_id comes from nextcloud_list_boards or what the confirm flag means in the call flow. The REST path template only echoes the parameter name.

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 names a specific verb and resource ("Delete one board") and scopes it to a single board, which is enough to separate it from nextcloud_delete_card, nextcloud_delete_stack, and nextcloud_list_boards. It stops short of explicitly contrasting itself with any sibling, so it sits just below 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?

There is no statement of when to use this versus alternatives or what preconditions apply (board ownership, admin rights). The only contextual hint is the parenthetical about restorability, which is behavioral rather than routing guidance. An agent must infer everything about usage from the tool name.

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