Skip to main content
Glama

delete_task

Remove a task from the Task MCP Server by specifying its ID to maintain an organized task list.

Instructions

Delete a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesID of the task to delete

Implementation Reference

  • The handler implementation for the `delete_task` tool, which removes a task from the in-memory tasks dictionary.
    elif name == "delete_task":
        task_id = int(arguments.get("task_id", 0))
        
        if task_id not in tasks:
            return [
                types.TextContent(
                    type="text",
                    text=f"❌ Task {task_id} not found"
                )
            ]
        
        deleted_task = tasks.pop(task_id)
        return [
            types.TextContent(
                type="text",
                text=f"🗑️ Task deleted: {deleted_task['title']}"
            )
        ]
  • The schema registration for the `delete_task` tool, defining the required `task_id` argument.
        name="delete_task",
        description="Delete a task",
        inputSchema={
            "type": "object",
            "properties": {
                "task_id": {
                    "type": "number",
                    "description": "ID of the task to delete"
                }
            },
            "required": ["task_id"]
        }
    )
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden. It states the tool is destructive ('Delete') but omits critical behavioral traits: whether deletion is permanent, recoverable, affects related data, or error cases (e.g., if task_id doesn't exist).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (3 words), but this manifests as under-specification rather than efficiency. Given the tool's destructive nature and sibling ambiguity, the sentence fails to earn its place by omitting necessary context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no annotations and no output schema, the description is incomplete. It lacks critical safety context (permanence, recovery options) and fails to clarify the distinction from 'complete_task', which is essential for correct agent selection.

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% and adequately documents the single 'task_id' parameter. The description adds no additional semantic value beyond what the schema already provides, meeting the baseline for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a task' restates the tool name with minimal elaboration (tautology). While the verb and resource are clear, it fails to distinguish from sibling 'complete_task', which may also remove a task from active work but with different semantics.

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?

Provides no guidance on when to use delete_task versus complete_task (permanent deletion vs. status change) or other alternatives. No prerequisites or conditions are mentioned.

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/devirokkam/MCP_Github_Deployment'

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