delega-mcp

delete_task

Permanently remove a task from the task management system using its unique task ID, keeping your task list accurate and up to date.

Instructions

Delete a task permanently

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

Input Schema

Name	Required	Description	Default
`task_id`	Yes	The task ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.19.0Sep 11, 2026
- removedInput schema / properties / task_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / task_id / type
```
Added value: +[
+  "string",
+  "number"
+]
```
Changed3 schema fields changedv1.2.1May 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / task_id / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]
```
- removedInput schema / properties / task_id / type
```
Removed value: -"integer"
```
First observedv1.0.3Mar 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that deletion is permanent (irreversible), but says nothing about required permissions, whether linked data/subtasks are cascaded, or whether repeated calls are idempotent.

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?

Five words with zero waste and the key constraint front-loaded. It is maximally concise, though arguably terse enough that useful context was omitted rather than trimmed.

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 one-parameter destructive tool with full schema coverage and no output schema, the description covers the core action and its permanence. It still leaves gaps an agent might care about, such as cascading effects and permission requirements.

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 description coverage is 100%, so the single task_id parameter is already fully documented as 'The task ID to delete'. The description adds no syntax, format, or constraint details beyond the schema, making the baseline 3 appropriate.

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 gives a specific verb (delete) and resource (task) plus the scope qualifier 'permanently'. It is clear what the tool does, though it does not name how it differs from related siblings like complete_task, set_task_state, or release_task.

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 guidance on when to use this tool versus alternatives. Siblings such as complete_task, set_task_state, and release_task change task status without deleting, and the description never tells the agent when deletion is the right choice.

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