Skip to main content
Glama

remove_todo

Delete a specific task from your software development plan by providing its unique identifier 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, calls storage.removeTodo, and returns success message.
    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}`,
          },
        ],
      };
    }
  • src/index.ts:169-182 (registration)
    Registers the 'remove_todo' tool in the list of available tools, including its 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'],
      },
    },
  • Core implementation that removes the specified todo from the plan by filtering the todos array and persisting changes to storage.
    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();
    }
  • Defines the input schema for the 'remove_todo' tool: requires a 'todoId' string.
    inputSchema: {
      type: 'object',
      properties: {
        todoId: {
          type: 'string',
          description: 'ID of the todo item to remove',
        },
      },
      required: ['todoId'],
    },
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. It states the tool performs a removal operation but doesn't clarify if this is destructive (permanent deletion vs. archiving), whether it requires specific permissions, what happens on success/failure, or if there are side effects (e.g., affecting other plan components). This leaves significant gaps for a mutation tool.

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?

The description is a single, straightforward sentence that efficiently conveys the core action. It's appropriately sized for a simple tool, though it could be slightly more front-loaded with key details like behavioral traits to improve structure.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical information about the operation's behavior (e.g., permanence, error handling), expected outcomes, or how it integrates with sibling tools like 'get_todos' or 'save_plan', leaving the agent with insufficient context.

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 'todoId' clearly documented in the schema. The description adds no additional parameter context beyond implying removal targets a todo item, which the schema already covers. This meets the baseline for high schema coverage.

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. However, it doesn't explicitly differentiate from sibling tools like 'update_todo_status' or 'save_plan' that might also affect todo items, which prevents a perfect score.

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' for marking todos as done or 'save_plan' for broader plan modifications. There's no mention of prerequisites (e.g., needing an existing todo item) or exclusions, leaving usage context vague.

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

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