kanboard-mcp

delete_comment

Permanently delete a Kanboard comment. Requires explicit confirmation to prevent accidental removal.

Instructions

Permanently delete a Kanboard comment. DESTRUCTIVE and irreversible — requires explicit confirm: true. To edit a comment's text instead of deleting it use update_comment. Returns { ok: true, comment_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": {
      "comment_id": "<comment_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_comment"
  }
}

Input Schema

Name	Required	Description	Default
`comment_id`	Yes	Comment 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.9/5.0

Behavior5/5

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

No annotations present, but description fully covers behavioral traits: destructiveness, irreversibility, required confirmation, and return format. No contradictions.

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?

Three sentences, no wasted words, front-loaded with purpose. Highly efficient.

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?

Complete for a simple deletion tool: covers purpose, parameters, usage constraints, alternative, and return value. No output schema needed.

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 100%, so baseline 3. Description reinforces the critical confirm parameter by calling out its necessity for destructive action, adding value beyond 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?

Clearly states the action (permanently delete a Kanboard comment), highlights destructiveness and irreversibility, and distinguishes from sibling tools like update_comment.

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

Usage Guidelines5/5

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

Explicitly states when to use (when you want to permanently delete) and provides alternative (use update_comment to edit instead). Also notes the required confirm: true.

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