Skip to main content
Glama

delete_task

Remove tasks from your TodoPomo workflow to maintain an organized task list and focus on current priorities.

Instructions

Delete a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID to delete

Implementation Reference

  • Handler for delete_task: finds task by ID in data.tasks, removes it using splice, saves data, returns success or error if not found.
    case "delete_task": {
      const taskIndex = data.tasks.findIndex((t) => t.id === args.taskId);
      if (taskIndex === -1) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({ success: false, error: "Task not found" }),
            },
          ],
        };
      }
      data.tasks.splice(taskIndex, 1);
      saveData(data);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              { success: true, message: "Task deleted successfully" },
              null,
              2
            ),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and inputSchema requiring taskId.
    {
      name: "delete_task",
      description: "Delete a task",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string", description: "Task ID to delete" },
        },
        required: ["taskId"],
      },
    },
  • src/index.ts:245-247 (registration)
    Registers all tools including delete_task by providing the TOOLS array in response to ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't specify whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting related pomodoro sessions). This is inadequate for a destructive operation.

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 extremely concise at three words, front-loading the essential action and resource. There's no wasted language or unnecessary elaboration, making it efficient for quick comprehension.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like what 'delete' entails (permanent vs. soft delete), error conditions, or return values. Given the complexity of deletion operations, this leaves significant gaps for the agent.

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%, with the single parameter 'taskId' clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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

Purpose3/5

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

The description states the verb ('Delete') and resource ('a task'), making the basic purpose clear. However, it lacks specificity about what constitutes a task in this system and doesn't differentiate from sibling tools like 'update_task' or 'list_tasks' beyond the obvious action difference.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., task must exist), consequences (e.g., permanent deletion), or when to choose deletion over updating or completing tasks. This leaves the agent with minimal context for decision-making.

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/PratyayRajak/todopomo-mcp'

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