Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

update_checklist_item

Modify an existing task in a structured checklist by updating its description, details, plan, or completion status to track progress on complex projects.

Instructions

Updates an existing checklist item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesThe index of the checklist item to update (0-based)
taskNoA short yet comprehensive name for the task
detailed_descriptionNoA longer description about what we want to achieve with this task
context_and_planNoRelated information, files the agent should read, and more details from other tasks, as well as a detailed plan for this task
doneNoWhether the task is completed

Implementation Reference

  • The handler function for the 'update_checklist_item' tool. It reads the task data, validates the index, updates the specified fields of the checklist item at that index (task, detailed_description, context_and_plan, done), recalculates progress, and writes back to the config file.
    private async updateChecklistItem(args: any): Promise<any> {
      if (args?.index === undefined) {
        throw new McpError(ErrorCode.InvalidParams, 'Index is required');
      }
    
      try {
        const taskData = await this.readTaskData();
        
        // Check if the index is valid
        if (args.index < 0 || args.index >= taskData.checklist.length) {
          throw new McpError(ErrorCode.InvalidParams, `Invalid index: ${args.index}`);
        }
        
        // Update the checklist item
        if (args.task !== undefined) {
          taskData.checklist[args.index].task = args.task;
        }
        
        if (args.detailed_description !== undefined) {
          taskData.checklist[args.index].detailed_description = args.detailed_description;
        }
        
        if (args.context_and_plan !== undefined) {
          taskData.checklist[args.index].context_and_plan = args.context_and_plan;
        }
        
        if (args.done !== undefined) {
          taskData.checklist[args.index].done = args.done;
        }
        
        // Write the updated task data to the file
        await this.writeTaskData(taskData);
        
        return {
          content: [
            {
              type: 'text',
              text: 'Checklist item updated successfully.',
            },
          ],
        };
      } catch (error) {
        console.error('Error updating checklist item:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error updating checklist item: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema definition for the 'update_checklist_item' tool, specifying the parameters including required index and optional fields to update.
    {
      name: 'update_checklist_item',
      description: 'Updates an existing checklist item.',
      inputSchema: {
        type: 'object',
        properties: {
          index: {
            type: 'number',
            description: 'The index of the checklist item to update (0-based)'
          },
          task: {
            type: 'string',
            description: 'A short yet comprehensive name for the task'
          },
          detailed_description: {
            type: 'string',
            description: 'A longer description about what we want to achieve with this task'
          },
          context_and_plan: {
            type: 'string',
            description: 'Related information, files the agent should read, and more details from other tasks, as well as a detailed plan for this task'
          },
          done: {
            type: 'boolean',
            description: 'Whether the task is completed'
          }
        },
        required: ['index']
      }
  • src/index.ts:432-433 (registration)
    The switch case in the CallToolRequestSchema handler that dispatches calls to the updateChecklistItem method.
    case 'update_checklist_item':
      return await this.updateChecklistItem(request.params.arguments);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Updates' implies a mutation, but the description doesn't specify whether this requires specific permissions, if changes are reversible, what happens to unspecified fields, or the expected response format. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and easy to parse, though it could be slightly more informative without sacrificing brevity (e.g., by hinting at updatable fields).

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 complexity of a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, side effects, or return values, and it lacks usage guidelines. While the schema handles parameter documentation well, the overall context for safe and effective use is insufficient.

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 schema description coverage is 100%, with all 5 parameters clearly documented in the input schema (e.g., 'index' as 0-based, 'task' as a short name). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Updates an existing checklist item' clearly states the verb ('Updates') and resource ('checklist item'), which is better than a tautology. However, it lacks specificity about what aspects can be updated and doesn't distinguish this tool from sibling tools like 'update_task_description' or 'update_metadata', which could also involve modifications to related entities.

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. It doesn't mention prerequisites (e.g., needing an existing checklist item), exclusions, or comparisons to siblings like 'mark_task_done' (which might overlap with the 'done' parameter) or 'remove_checklist_item' (for deletion). Without such context, an agent might struggle to select the appropriate tool.

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/landicefu/divide-and-conquer-mcp-server'

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