kanboard-mcp

delete_task

Permanently remove a Kanboard task from your project. Requires explicit confirmation to prevent accidental deletion.

Instructions

Permanently delete a Kanboard task. DESTRUCTIVE and irreversible — requires explicit confirm: true. Returns { ok: true, task_id } on success.

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": {
      "task_id": "<task_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task id to permanently delete (required).
`confirm`	Yes	Must be exactly `true` to confirm permanent deletion.

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description discloses that the operation is destructive and irreversible, and specifies the return format. This is sufficient for a simple deletion action, though additional details (e.g., authorization needs) could enhance transparency.

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?

The description is extremely concise: a single sentence that conveys purpose, behavioral traits, and return format without any unnecessary words.

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 delete tool with no output schema, the description covers the action, destructive nature, confirm requirement, and return structure. It lacks mention of prerequisites like task existence, but this is implicitly understood.

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 100% and both parameters are well-described in the schema. The description reinforces the 'confirm' requirement but adds no new semantic information beyond the schema.

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 description clearly states 'Permanently delete a Kanboard task', specifying a specific verb and resource. It distinguishes itself from sibling tools like delete_comment or delete_subtask by focusing on tasks.

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?

The description explicitly notes that the action is destructive and requires 'confirm: true', providing clear usage context. However, it does not mention alternative non-destructive actions like close_task for reversible closure.

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