Skip to main content
Glama
PhilippMT

Software Planning Tool

by PhilippMT

remove_todo

Delete a specific task from your software development plan by providing its unique ID to maintain an organized project workflow.

Instructions

Remove a todo item from the current plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todoIdYesID of the todo item to remove

Implementation Reference

  • MCP tool handler for 'remove_todo': validates current goal, extracts todoId from arguments, delegates to storage.removeTodo, and returns success response.
    case 'remove_todo': {
      if (!this.currentGoal) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'No active goal. Start a new planning session first.'
        );
      }
    
      const { todoId } = request.params.arguments as { todoId: string };
      await storage.removeTodo(this.currentGoal.id, todoId);
    
      return {
        content: [
          {
            type: 'text',
            text: `Successfully removed todo ${todoId}`,
          },
        ],
      };
    }
  • Input schema for the 'remove_todo' tool defining the required 'todoId' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        todoId: {
          type: 'string',
          description: 'ID of the todo item to remove',
        },
      },
      required: ['todoId'],
    },
  • src/index.ts:169-182 (registration)
    Registration of the 'remove_todo' tool in the tools list for ListToolsRequestSchema, including name, description, and input schema.
    {
      name: 'remove_todo',
      description: 'Remove a todo item from the current plan',
      inputSchema: {
        type: 'object',
        properties: {
          todoId: {
            type: 'string',
            description: 'ID of the todo item to remove',
          },
        },
        required: ['todoId'],
      },
    },
  • Helper method in storage class that removes a todo item by ID from the plan's todos array, updates the plan timestamp, and persists the change.
    async removeTodo(goalId: string, todoId: string): Promise<void> {
      const plan = await this.getPlan(goalId);
      if (!plan) {
        throw new Error(`No plan found for goal ${goalId}`);
      }
    
      plan.todos = plan.todos.filter((todo: Todo) => todo.id !== todoId);
      plan.updatedAt = new Date().toISOString();
      await this.save();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool removes a todo item, implying a destructive mutation, but doesn't clarify if this is permanent, reversible, requires specific permissions, or affects other plan components. For a mutation tool with zero annotation coverage, this is a significant gap in transparency, as it omits critical behavioral traits like side effects or error conditions.

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 a single, front-loaded sentence that efficiently conveys the core action without unnecessary words. Every part ('Remove a todo item from the current plan') earns its place by specifying the verb, resource, and context, making it highly concise and well-structured for quick understanding.

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?

Given the tool's complexity as a destructive mutation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permanence, permissions), output expectations, or error handling. While the purpose is clear, the context for safe and effective use is insufficient, especially compared to siblings that might offer more guidance or structured returns.

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?

The input schema has 100% description coverage, with 'todoId' clearly documented as the ID of the todo item to remove. The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract from the schema's documentation.

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 clearly states the action ('Remove') and resource ('a todo item from the current plan'), making the purpose immediately understandable. It distinguishes from siblings like 'add_todo' and 'update_todo_status' by specifying removal rather than addition or modification. However, it doesn't explicitly differentiate from potential deletion operations in other contexts, keeping it at 4 rather than 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_todo_status' (which might mark as done instead of remove) or 'save_plan' (which might handle broader plan modifications). It lacks explicit when/when-not instructions or prerequisite context, such as requiring an existing todo or plan, leaving usage ambiguous beyond the basic purpose.

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/PhilippMT/Software-planning-mcp'

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