Skip to main content
Glama
PhilippMT

Software Planning Tool

by PhilippMT

update_todo_status

Mark a task as complete or incomplete in your software project plan by providing its ID and desired status.

Instructions

Update the completion status of a todo item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todoIdYesID of the todo item
isCompleteYesNew completion status

Implementation Reference

  • The MCP tool handler for 'update_todo_status' which validates the current goal exists, extracts todoId and isComplete from arguments, calls storage.updateTodoStatus, and returns the updated todo as JSON.
    case 'update_todo_status': {
      if (!this.currentGoal) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'No active goal. Start a new planning session first.'
        );
      }
    
      const { todoId, isComplete } = request.params.arguments as {
        todoId: string;
        isComplete: boolean;
      };
      const updatedTodo = await storage.updateTodoStatus(
        this.currentGoal.id,
        todoId,
        isComplete
      );
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(updatedTodo, null, 2),
          },
        ],
      };
    }
  • Input schema for the 'update_todo_status' tool, defining required parameters todoId (string) and isComplete (boolean).
    {
      name: 'update_todo_status',
      description: 'Update the completion status of a todo item',
      inputSchema: {
        type: 'object',
        properties: {
          todoId: {
            type: 'string',
            description: 'ID of the todo item',
          },
          isComplete: {
            type: 'boolean',
            description: 'New completion status',
          },
        },
        required: ['todoId', 'isComplete'],
      },
    },
  • src/index.ts:111-210 (registration)
    Registration of tools list including 'update_todo_status' in the ListToolsRequestHandler.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        {
          name: 'start_planning',
          description: 'Start a new planning session with a goal',
          inputSchema: {
            type: 'object',
            properties: {
              goal: {
                type: 'string',
                description: 'The software development goal to plan',
              },
            },
            required: ['goal'],
          },
        },
        {
          name: 'save_plan',
          description: 'Save the current implementation plan',
          inputSchema: {
            type: 'object',
            properties: {
              plan: {
                type: 'string',
                description: 'The implementation plan text to save',
              },
            },
            required: ['plan'],
          },
        },
        {
          name: 'add_todo',
          description: 'Add a new todo item to the current plan',
          inputSchema: {
            type: 'object',
            properties: {
              title: {
                type: 'string',
                description: 'Title of the todo item',
              },
              description: {
                type: 'string',
                description: 'Detailed description of the todo item',
              },
              complexity: {
                type: 'number',
                description: 'Complexity score (0-10)',
                minimum: 0,
                maximum: 10,
              },
              codeExample: {
                type: 'string',
                description: 'Optional code example',
              },
            },
            required: ['title', 'description', 'complexity'],
          },
        },
        {
          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'],
          },
        },
        {
          name: 'get_todos',
          description: 'Get all todos in the current plan',
          inputSchema: {
            type: 'object',
            properties: {},
          },
        },
        {
          name: 'update_todo_status',
          description: 'Update the completion status of a todo item',
          inputSchema: {
            type: 'object',
            properties: {
              todoId: {
                type: 'string',
                description: 'ID of the todo item',
              },
              isComplete: {
                type: 'boolean',
                description: 'New completion status',
              },
            },
            required: ['todoId', 'isComplete'],
          },
        },
      ],
    }));
  • Helper method in storage class that locates the todo by ID within the goal's plan, updates its completion status and timestamps, persists to file, and returns the updated todo.
    async updateTodoStatus(goalId: string, todoId: string, isComplete: boolean): Promise<Todo> {
      const plan = await this.getPlan(goalId);
      if (!plan) {
        throw new Error(`No plan found for goal ${goalId}`);
      }
    
      const todo = plan.todos.find((t: Todo) => t.id === todoId);
      if (!todo) {
        throw new Error(`No todo found with id ${todoId}`);
      }
    
      todo.isComplete = isComplete;
      todo.updatedAt = new Date().toISOString();
      plan.updatedAt = new Date().toISOString();
      await this.save();
      return todo;
    }
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 this is an update operation, implying mutation, but doesn't address permissions, side effects, error conditions, or response format. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple update operation and front-loads the essential information.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after the update (e.g., success confirmation, error responses), nor does it cover behavioral aspects like permissions or side effects, leaving the agent with critical gaps.

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 both parameters clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema (e.g., format constraints or examples). The baseline score of 3 reflects adequate but minimal value addition.

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 verb ('update') and resource ('completion status of a todo item'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling operations like 'add_todo' or 'remove_todo' beyond the obvious status update focus, 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 'add_todo' for creating todos or 'get_todos' for checking status. There's no mention of prerequisites (e.g., needing an existing todo ID) or contextual constraints, leaving usage entirely implicit.

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