Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

mark_task_undone

Reverts a completed checklist item to an incomplete status to correct errors or adjust task progress in structured workflows.

Instructions

Marks a checklist item as not done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesThe index of the checklist item to mark as not done (0-based)

Implementation Reference

  • Implements the core logic for the mark_task_undone tool: validates index, reads task data, sets checklist item done to false, updates progress by saving to file, returns success message.
    private async markTaskUndone(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}`);
        }
        
        // Mark the checklist item as not done
        taskData.checklist[args.index].done = false;
        
        // Write the updated task data to the file
        await this.writeTaskData(taskData);
        
        return {
          content: [
            {
              type: 'text',
              text: 'Task marked as not done.',
            },
          ],
        };
      } catch (error) {
        console.error('Error marking task as not done:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error marking task as not done: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Defines the input schema for the mark_task_undone tool in the ListTools response, specifying required 'index' parameter.
    {
      name: 'mark_task_undone',
      description: 'Marks a checklist item as not done.',
      inputSchema: {
        type: 'object',
        properties: {
          index: {
            type: 'number',
            description: 'The index of the checklist item to mark as not done (0-based)'
          }
        },
        required: ['index']
      }
  • src/index.ts:436-437 (registration)
    Registers the tool handler in the CallToolRequest switch statement, routing calls to the markTaskUndone method.
    case 'mark_task_undone':
      return await this.markTaskUndone(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. It states the mutation action ('marks') but doesn't describe side effects (e.g., whether this triggers notifications, updates timestamps, or affects task completion status), error conditions, or response format. The description is minimal and lacks operational context.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable.

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 inadequate. It doesn't explain what the tool returns, error handling, or behavioral implications. Given the sibling tools include multiple checklist operations, more context about how this fits into the workflow is needed.

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 a single well-documented parameter ('index'), so the baseline is 3. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain what happens if the index is invalid or out of bounds).

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 ('marks') and the resource ('checklist item') with the specific state change ('as not done'). It distinguishes from 'mark_task_done' by specifying the opposite state, but doesn't explicitly differentiate from other checklist-related tools like 'clear_task' or 'update_checklist_item'.

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 'mark_task_done', 'clear_task', or 'update_checklist_item'. It doesn't mention prerequisites (e.g., that the item must exist or be currently marked as done) or contextual constraints.

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