Skip to main content
Glama

delete_task_file

Permanently delete a file attachment from a Kanboard task. Requires explicit confirmation to avoid accidental removal.

Instructions

Permanently delete a file attachment from a Kanboard task. DESTRUCTIVE — requires explicit confirm: true. Returns { ok: true, file_id } on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesFile id to permanently delete (required).
confirmYesMust be exactly `true` to confirm permanent deletion.

Implementation Reference

  • KanboardHandler.removeTaskFile — calls Kanboard's removeTaskFile JSON-RPC method with file_id. This is the underlying API call executed by the tool handler.
    /**
     * Permanently removes a task attachment (file).
     * Kanboard's wire param for this method is `file_id`.
     * @throws {KanboardApiError} when Kanboard returns false.
     */
    public async removeTaskFile(fileId: number): Promise<void> {
      const raw = await this.#apiClient.call("removeTaskFile", { file_id: fileId });
      this.#logger.debug({ method: "removeTaskFile" }, "removeTaskFile OK");
      decodeMutation("removeTaskFile", raw);
    }
  • assertConfirmed helper used by the tool handler to enforce confirm: true before performing the destructive delete.
    export function assertConfirmed(toolName: string, confirm: boolean): void {
      // Strict identity check via Object.is rather than `!== true`:
      // - keeps the lint rule happy (no boolean-literal compare)
      // - still rejects ANY non-`true` value, including 1, "true", undefined.
      if (!Object.is(confirm, true)) {
        throw new ValidationError(
          toolName,
          `${toolName}: this is a destructive operation — pass confirm: true to proceed.`,
        );
      }
    }
Behavior5/5

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

With no annotations, the description fully carries the burden, disclosing that the operation is permanent and requires explicit confirmation. It also specifies the return value, ensuring the agent knows what to expect.

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 two sentences, front-loading the purpose and then adding essential usage and return details. Every sentence is meaningful and there is no unnecessary text.

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?

Given the simplicity of the tool (two parameters, no output schema, no nested objects), the description adequately covers purpose, behavior, confirm requirement, and return value. It is complete for the agent to use correctly.

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?

The input schema has 100% coverage with descriptions for both parameters. The description adds value by emphasizing the confirm parameter's requirement to be exactly true and by stating the return format, which is not in 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 states 'Permanently delete a file attachment from a Kanboard task' with a specific verb and resource, clearly distinguishing it from sibling tools like delete_task which deletes the entire task.

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 'DESTRUCTIVE — requires explicit `confirm: true`', providing clear guidance on how to use the tool safely. However, it does not mention alternatives or when not to use it, though the condition is well-stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ErnestoCorona/kanboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server