Skip to main content
Glama
landicefu

Divide and Conquer MCP Server

by landicefu

add_note

Adds a note to a task to preserve context, track progress, and maintain structured information during complex task breakdowns.

Instructions

Adds a note to the task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe content of the note

Implementation Reference

  • The handler function that executes the add_note tool logic: validates content, reads task data, appends note with timestamp to notes array, persists to config file, returns success message.
    private async addNote(args: any): Promise<any> {
      if (!args?.content) {
        throw new McpError(ErrorCode.InvalidParams, 'Note content is required');
      }
    
      try {
        const taskData = await this.readTaskData();
        
        // Initialize the notes array if it doesn't exist
        if (!taskData.notes) {
          taskData.notes = [];
        }
        
        // Add the note
        taskData.notes.push({
          timestamp: new Date().toISOString(),
          content: args.content
        });
        
        // Write the updated task data to the file
        await this.writeTaskData(taskData);
        
        return {
          content: [
            {
              type: 'text',
              text: 'Note added successfully.',
            },
          ],
        };
      } catch (error) {
        console.error('Error adding note:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Error adding note: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for the add_note tool, requiring a 'content' string.
    inputSchema: {
      type: 'object',
      properties: {
        content: {
          type: 'string',
          description: 'The content of the note'
        }
      },
      required: ['content']
    }
  • src/index.ts:442-443 (registration)
    Dispatch case in the main tool request handler switch statement that calls the addNote handler for 'add_note' tool.
    case 'add_note':
      return await this.addNote(request.params.arguments);
  • src/index.ts:324-337 (registration)
    Tool object in the tools list registered via server.setTools, defining name, description, and input schema for add_note.
    {
      name: 'add_note',
      description: 'Adds a note to the task.',
      inputSchema: {
        type: 'object',
        properties: {
          content: {
            type: 'string',
            description: 'The content of the note'
          }
        },
        required: ['content']
      }
    },
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 'Adds a note' which implies a write/mutation operation, but doesn't clarify permissions, side effects (e.g., if it updates timestamps), or error conditions. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 that states the core purpose without any wasted words. It's appropriately sized for a simple tool and front-loads the essential information ('Adds a note to the task'). Every word earns its place.

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 this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after adding (e.g., success confirmation, error responses), how notes relate to the task lifecycle, or any behavioral constraints. For a tool that modifies state, more context is needed to use it effectively.

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 description adds no parameter information beyond what's in the schema, which has 100% coverage with a clear description for the single 'content' parameter. Since schema_description_coverage is high, the baseline is 3 even without additional param details in the description. The description doesn't compensate but doesn't need to given the schema's completeness.

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 ('Adds') and target resource ('a note to the task'), making the purpose immediately understandable. It distinguishes from siblings like 'add_checklist_item' or 'add_resource' by specifying 'note' rather than other task components. However, it doesn't explicitly contrast with all siblings, missing a perfect 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. It doesn't mention prerequisites (e.g., needing an existing task), exclusions, or comparisons to similar tools like 'update_context' or 'update_task_description'. Without such context, an agent might struggle with tool selection.

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