Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_task

Destructive

Permanently remove a task by ID with explicit confirmation. Use when full deletion is required, not just marking done, which preserves history.

Instructions

DESTRUCTIVE & IRREVERSIBLE: permanently delete a task. Prefer complete_task to mark a task done while keeping it in history. Requires confirm=true. Idempotent on retry: response is {deleted: true, alreadyDeleted: false, id} on a fresh delete or {deleted: true, alreadyDeleted: true, id} if the task was already gone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
confirmYesMust be set to true. Permanently deletes the task. To mark done without losing history use complete_task. Irreversible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / required
      Previous value: -[
-  "confirm"
-]New value: +[
+  "id",
+  "confirm"
+]
  2. Addedv1.7.0
  3. Removedv1.6.2
  4. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description adds the precise idempotency contract with example response payloads for fresh vs already-deleted tasks. It also warns irreversibility and requires confirm=true, giving the agent full behavioral expectations. No contradiction with annotations.

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 with the destructive warning and primary purpose front-loaded, followed by the alternative, the precondition, and the idempotency contract. No filler or repetition of schema information that is already present.

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?

With no output schema, the description provides the complete response contract for both fresh and repeated deletes. It covers the core action, the safer alternative, the required flag, and retry semantics, making it self-sufficient for an agent to invoke 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 schema only documents confirm (50% coverage) while id lacks a description. The description compensates by establishing the confirm requirement and defining the response uses id, making the id's role clear. The schema's numeric constraints on id remain the reference for validation, and the description adds just enough semantic context.

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 opens with 'DESTRUCTIVE & IRREVERSIBLE: permanently delete a task,' naming the exact verb, resource, and consequence. It explicitly contrasts with complete_task, which marks a task done while preserving history, so it is easily distinguishable from the sibling that looks most similar.

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 instructs 'Prefer complete_task to mark a task done while keeping it in history,' giving a clear when-not-to-use condition and naming the alternative. It also states the mandatory confirm=true precondition and documents idempotent retry behavior, leaving no doubt about invocation.

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