Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

get_checklist_summary

Generate a summary of checklist items with completion status to track task progress and monitor completion rates.

Instructions

Returns a summary of the checklist with completion status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_descriptionsNoWhether to include detailed descriptions in the summary

Implementation Reference

  • The main execution logic for the get_checklist_summary tool. Reads task data, builds a markdown summary of progress and checklist items (optionally including descriptions), and returns it as MCP content.
    private async getChecklistSummary(args: any): Promise<any> {
      try {
        const taskData = await this.readTaskData();
        
        // Generate the summary
        const includeDescriptions = args?.include_descriptions || false;
        
        let summary = `# Task: ${taskData.task_description}\n\n`;
        
        if (taskData.context_for_all_tasks) {
          summary += `## Context\n\n${taskData.context_for_all_tasks}\n\n`;
        }
        
        summary += `## Progress: ${taskData.metadata.progress.completed}/${taskData.metadata.progress.total} (${taskData.metadata.progress.percentage}%)\n\n`;
        
        summary += '## Checklist\n\n';
        
        taskData.checklist.forEach((item, index) => {
          const checkbox = item.done ? '[x]' : '[ ]';
          summary += `${index}. ${checkbox} ${item.task}\n`;
          
          if (includeDescriptions) {
            if (item.detailed_description) {
              summary += `   - Description: ${item.detailed_description.replace(/\n/g, '\n     ')}\n`;
            }
            
            // Context is intentionally excluded from summary to save context window space
          }
        });
        
        return {
          content: [
            {
              type: 'text',
              text: summary,
            },
          ],
        };
      } catch (error) {
        console.error('Error getting checklist summary:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error getting checklist summary: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the get_checklist_summary tool, specifying an optional boolean parameter to include detailed descriptions.
    inputSchema: {
      type: 'object',
      properties: {
        include_descriptions: {
          type: 'boolean',
          description: 'Whether to include detailed descriptions in the summary',
          default: false
        }
      }
    }
  • src/index.ts:394-407 (registration)
    Tool registration entry in the ListTools response, defining name, description, and input schema.
    {
      name: 'get_checklist_summary',
      description: 'Returns a summary of the checklist with completion status.',
      inputSchema: {
        type: 'object',
        properties: {
          include_descriptions: {
            type: 'boolean',
            description: 'Whether to include detailed descriptions in the summary',
            default: false
          }
        }
      }
    },
  • src/index.ts:450-451 (registration)
    Dispatch case in the CallToolRequest handler that routes calls to the getChecklistSummary method.
    case 'get_checklist_summary':
      return await this.getChecklistSummary(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. It mentions 'completion status' but doesn't explain what that entails (e.g., percentages, counts, or detailed breakdowns), nor does it cover potential side effects, error conditions, or response format. This leaves significant gaps for a tool that likely returns structured data.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded with the main action, though it could be slightly more structured by explicitly mentioning the parameter's role, but overall it's concise and effective.

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 lack of annotations and output schema, the description is incomplete. It doesn't specify what the summary includes beyond 'completion status' (e.g., item counts, metadata), nor does it address how results are formatted or potential limitations. For a tool with no structured output documentation, this leaves too much ambiguity for reliable agent use.

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 the single parameter 'include_descriptions' well-documented in the schema. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline score of 3 for adequate but not enhanced coverage.

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 tool's purpose with a specific verb ('Returns') and resource ('summary of the checklist'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'get_current_task_details' or 'update_metadata', which might also provide checklist-related information, so it doesn't reach the highest score.

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 siblings like 'get_current_task_details' that might overlap in functionality, there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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