Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

remove_checklist_item

Remove a specific item from a checklist by its index position to maintain task organization and progress tracking.

Instructions

Removes a checklist item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesThe index of the checklist item to remove (0-based)

Implementation Reference

  • The core handler function that validates the index parameter, reads the task data, removes the checklist item using array.splice, updates progress by saving to file, and returns success or error response.
    private async removeChecklistItem(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}`);
        }
        
        // Remove the checklist item
        taskData.checklist.splice(args.index, 1);
        
        // Write the updated task data to the file
        await this.writeTaskData(taskData);
        
        return {
          content: [
            {
              type: 'text',
              text: 'Checklist item removed successfully.',
            },
          ],
        };
      } catch (error) {
        console.error('Error removing checklist item:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error removing checklist item: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition requiring a numeric 'index' (0-based) for the checklist item to remove.
    inputSchema: {
      type: 'object',
      properties: {
        index: {
          type: 'number',
          description: 'The index of the checklist item to remove (0-based)'
        }
      },
      required: ['index']
    }
  • src/index.ts:292-305 (registration)
    Tool registration in the ListTools handler, providing name, description, and input schema.
    {
      name: 'remove_checklist_item',
      description: 'Removes a checklist item.',
      inputSchema: {
        type: 'object',
        properties: {
          index: {
            type: 'number',
            description: 'The index of the checklist item to remove (0-based)'
          }
        },
        required: ['index']
      }
    },
  • src/index.ts:438-439 (registration)
    Dispatch case in the CallToolRequest handler that routes to the removeChecklistItem method.
    case 'remove_checklist_item':
      return await this.removeChecklistItem(request.params.arguments);
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. 'Removes' implies a destructive mutation, but there's no information about whether this requires specific permissions, whether the removal is permanent or reversible, what happens to checklist indices after removal, or what the response looks like. The description doesn't compensate for the lack of annotations.

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 maximally concise - a single sentence with zero wasted words. It's front-loaded with the core action and target. Every word earns its place, 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 destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like permanence, error conditions, or response format. Given the complexity of checklist manipulation and multiple sibling alternatives, more context about when and how to use this specific tool would be valuable.

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 'index' fully documented in the schema as 'The index of the checklist item to remove (0-based)'. The description adds no additional parameter information beyond what the schema provides, meeting the baseline expectation when schema coverage is complete.

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 ('removes') and target ('checklist item'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'clear_task' or 'reorder_checklist_item' that also modify checklists, missing the opportunity to clarify its specific scope within the checklist management domain.

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. With multiple sibling tools that manipulate checklists (add_checklist_item, reorder_checklist_item, update_checklist_item, clear_task), there's no indication of when removal is appropriate versus clearing or updating. No prerequisites or exclusions are mentioned.

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