Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

update_task_description

Modify the main task description to reflect changes in requirements or scope within the Divide and Conquer MCP Server's structured task management system.

Instructions

Updates the main task description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_descriptionYesThe new task description

Implementation Reference

  • The main handler function that reads the current task data from file, updates the task_description field with the provided argument, persists the changes using writeTaskData, and returns a success or error message.
    private async updateTaskDescription(args: any): Promise<any> {
      if (!args?.task_description) {
        throw new McpError(ErrorCode.InvalidParams, 'Task description is required');
      }
    
      try {
        const taskData = await this.readTaskData();
        
        // Update the task description
        taskData.task_description = args.task_description;
        
        // Write the updated task data to the file
        await this.writeTaskData(taskData);
        
        return {
          content: [
            {
              type: 'text',
              text: 'Task description updated successfully.',
            },
          ],
        };
      } catch (error) {
        console.error('Error updating task description:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error updating task description: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:175-188 (registration)
    Registers the 'update_task_description' tool in the MCP server's list of tools, including its name, description, and input schema for validation.
    {
      name: 'update_task_description',
      description: 'Updates the main task description.',
      inputSchema: {
        type: 'object',
        properties: {
          task_description: {
            type: 'string',
            description: 'The new task description'
          }
        },
        required: ['task_description']
      }
    },
  • Defines the input schema for the tool, requiring a 'task_description' string.
    inputSchema: {
      type: 'object',
      properties: {
        task_description: {
          type: 'string',
          description: 'The new task description'
        }
      },
      required: ['task_description']
  • Switch case in the main CallToolRequestSchema handler that routes calls to the updateTaskDescription method.
    case 'update_task_description':
      return await this.updateTaskDescription(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 but only states it 'updates' without disclosing behavioral traits such as permissions needed, whether changes are reversible, or how it interacts with other task operations. It lacks details on mutation effects, error conditions, or response format.

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 waste, front-loading the core action. It's appropriately sized for a simple tool, though brevity contributes to gaps in other dimensions.

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 doesn't explain what 'updates' entails (e.g., overwrites or merges), potential side effects, or return values, leaving significant gaps for agent understanding.

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 parameter 'task_description' documented as 'The new task description'. The description adds no additional meaning beyond this, as it doesn't elaborate on format, constraints, or examples. Baseline 3 is appropriate since 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 the main task description' clearly states the action (updates) and target (main task description), but it's somewhat vague about what constitutes the 'main' description versus other task-related fields. It distinguishes from siblings like 'update_checklist_item' or 'update_metadata' by focusing on description, but could be more specific about scope.

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?

No guidance is provided on when to use this tool versus alternatives like 'update_metadata' or 'update_context', nor any prerequisites (e.g., requires an existing task). The description implies usage for modifying descriptions but offers no explicit context or exclusions.

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