Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

get_current_task_details

Retrieve details of the current uncompleted task with full context to understand what needs to be done next in complex task breakdown workflows.

Instructions

Retrieves details of the current task (first uncompleted task) with full context. This is the recommended tool to use when working with tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'get_current_task_details'. It reads the current task data, identifies the first uncompleted checklist item as the current task, provides full details for it and limited details for others (excluding context_and_plan), formats a structured response with ultimate goal, tasks list, context, progress, metadata, notes, and resources, and returns it as JSON text content.
    private async getCurrentTaskDetails(): Promise<any> {
      try {
        const taskData = await this.readTaskData();
        
        // Find the first uncompleted task
        const currentTaskIndex = taskData.checklist.findIndex(item => !item.done);
        
        // Process all tasks with different detail levels
        const tasks = taskData.checklist.map((item, index) => {
          if (index === currentTaskIndex) {
            // For the current task (first uncompleted), include all fields
            return {
              index,
              ...item,
              is_current: true
            };
          } else {
            // For other tasks, exclude context_and_plan to save context window space
            const { context_and_plan, ...taskWithoutContext } = item;
            return {
              index,
              ...taskWithoutContext,
              is_current: false
            };
          }
        });
        
        // Format the response
        let response = {
          ultimate_goal: {
            description: taskData.task_description,
            note: "This is the final goal of the entire task, not just the current step."
          },
          current_task_index: currentTaskIndex,
          tasks: tasks,
          context_for_all_tasks: taskData.context_for_all_tasks || "",
          progress: taskData.metadata.progress,
          metadata: taskData.metadata,
          notes: taskData.notes || [],
          resources: taskData.resources || []
        };
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error('Error getting current task details:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error getting current task details: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The schema definition for the 'get_current_task_details' tool, including name, description, and empty input schema (no parameters required). This is part of the tools list returned by ListToolsRequest.
    {
      name: 'get_current_task_details',
      description: 'Retrieves details of the current task (first uncompleted task) with full context. This is the recommended tool to use when working with tasks.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    }
  • src/index.ts:452-453 (registration)
    The registration/dispatch case in the CallToolRequestHandler switch statement that calls the getCurrentTaskDetails handler when the tool name matches.
    case 'get_current_task_details':
      return await this.getCurrentTaskDetails();
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions retrieving 'full context' but doesn't disclose what that includes (e.g., checklist items, notes, metadata), whether it's a read-only operation (implied but not stated), or any behavioral traits like permissions needed or rate limits. The description adds minimal behavioral context beyond the basic purpose.

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 two concise sentences with zero waste. The first sentence states the purpose and scope, and the second provides usage guidance. It's front-loaded with essential information and appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and low complexity (0 parameters), the description is adequate but has gaps. It explains what the tool does and when to use it, but lacks details on return values (e.g., what 'full context' includes) and behavioral traits. For a read operation with no structured output documentation, this is minimally viable but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and a baseline of 4 is appropriate for a zero-parameter tool where the schema fully covers the input structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Retrieves details') and resource ('current task'), with additional context about scope ('first uncompleted task' and 'full context'). It effectively distinguishes this read operation from sibling tools that modify tasks (e.g., mark_task_done, update_task_description).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'This is the recommended tool to use when working with tasks,' providing clear guidance on when to use it versus alternatives. It positions this as the primary tool for task context retrieval, though it doesn't specify when not to use it or name specific alternatives.

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