Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

update_metadata

Modify task metadata including priority, tags, and estimated completion time to organize and track progress in complex task breakdowns.

Instructions

Updates the task metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to categorize the task
priorityNoPriority level of the task
estimated_completion_timeNoEstimated completion time (ISO timestamp or duration)

Implementation Reference

  • The main handler function for the 'update_metadata' tool. Reads current task data from config file, conditionally updates metadata fields (tags, priority, estimated_completion_time) based on input arguments, persists changes by calling writeTaskData, and returns a standardized MCP response with success or error message.
    private async updateMetadata(args: any): Promise<any> {
      try {
        const taskData = await this.readTaskData();
        
        // Update the metadata
        if (args.tags !== undefined) {
          taskData.metadata.tags = args.tags;
        }
        
        if (args.priority !== undefined) {
          taskData.metadata.priority = args.priority;
        }
        
        if (args.estimated_completion_time !== undefined) {
          taskData.metadata.estimated_completion_time = args.estimated_completion_time;
        }
        
        // Write the updated task data to the file
        await this.writeTaskData(taskData);
        
        return {
          content: [
            {
              type: 'text',
              text: 'Metadata updated successfully.',
            },
          ],
        };
      } catch (error) {
        console.error('Error updating metadata:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error updating metadata: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:360-384 (registration)
    Tool registration in the ListToolsRequestSchema handler. Defines the tool name, description, and inputSchema which validates optional updates to tags (array of strings), priority (enum: high/medium/low), and estimated_completion_time (string).
    {
      name: 'update_metadata',
      description: 'Updates the task metadata.',
      inputSchema: {
        type: 'object',
        properties: {
          tags: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'Tags to categorize the task'
          },
          priority: {
            type: 'string',
            enum: ['high', 'medium', 'low'],
            description: 'Priority level of the task'
          },
          estimated_completion_time: {
            type: 'string',
            description: 'Estimated completion time (ISO timestamp or duration)'
          }
        }
      }
    },
  • src/index.ts:446-447 (registration)
    Routing case in the CallToolRequestSchema switch statement that dispatches 'update_metadata' calls to the private updateMetadata handler method.
    case 'update_metadata':
      return await this.updateMetadata(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. 'Updates' implies a mutation operation, but the description doesn't mention permissions required, whether changes are reversible, side effects, or response format. This leaves significant gaps for a tool that modifies task data.

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 ('Updates'), making it immediately clear. Every word earns its place, achieving optimal conciseness for the minimal information provided.

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 no annotations and no output schema, the description is incomplete for a mutation tool. It lacks details on behavioral traits (e.g., permissions, idempotency), doesn't clarify the relationship with sibling update tools, and provides minimal context beyond the basic purpose. This is inadequate for safe and effective use by an AI agent.

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 clear descriptions for all three parameters (tags, priority, estimated_completion_time). The description doesn't add any meaning beyond what the schema provides, such as explaining how these fields relate to 'metadata' or usage 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 task metadata' clearly states the verb ('Updates') and resource ('task metadata'), making the basic purpose understandable. However, it doesn't specify what constitutes 'metadata' or distinguish this tool from sibling tools like 'update_task_description' or 'update_context', leaving room for ambiguity 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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'update_task_description', 'update_context', and 'mark_task_done', there's no indication of whether this tool is for specific metadata fields or general updates, nor any prerequisites or exclusions 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