Skip to main content
Glama

update_todo_status

Mark todo items as complete or incomplete to track progress in software development planning. Update status by providing the todo ID and new completion state.

Instructions

Update the completion status of a todo item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todoIdYesID of the todo item
isCompleteYesNew completion status

Implementation Reference

  • MCP tool handler for 'update_todo_status': checks for active goal, extracts todoId and isComplete from arguments, updates via storage, returns 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),
          },
        ],
      };
    }
  • src/index.ts:191-208 (registration)
    Tool registration in ListTools handler, including name, description, and input schema for 'update_todo_status'.
    {
      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'],
      },
    },
  • Storage helper function that updates the completion status of a specific todo in the plan and persists the changes.
    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 'Update' which implies a mutation, but doesn't clarify permissions, side effects (e.g., whether it triggers notifications), error conditions, or response format. This is inadequate for a mutation tool without annotation support.

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 front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 incomplete. It lacks critical context such as what the tool returns, error handling, authentication requirements, or how it differs behaviorally from sibling tools. The high schema coverage doesn't compensate for these 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%, so the schema fully documents both parameters ('todoId' and 'isComplete'). The description adds no additional parameter semantics beyond what's in the schema, but the baseline is 3 when schema coverage is high and no parameters are omitted.

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 ('Update') and resource ('completion status of a todo item'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'add_todo' or 'remove_todo' beyond the status 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' or 'remove_todo'. It doesn't mention prerequisites (e.g., needing an existing todo ID) or contextual constraints, leaving the agent to infer usage from the tool name alone.

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