Skip to main content
Glama
PhilippMT

Software Planning Tool

by PhilippMT

add_todo

Add a new task to your software development plan with title, description, complexity score, and optional code examples for better project management.

Instructions

Add a new todo item to the current plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the todo item
descriptionYesDetailed description of the todo item
complexityYesComplexity score (0-10)
codeExampleNoOptional code example

Implementation Reference

  • MCP tool handler for 'add_todo': validates current goal exists, casts arguments to Todo shape, calls storage.addTodo, and returns the new todo as JSON text.
    case 'add_todo': {
      if (!this.currentGoal) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'No active goal. Start a new planning session first.'
        );
      }
    
      const todo = request.params.arguments as Omit<
        Todo,
        'id' | 'isComplete' | 'createdAt' | 'updatedAt'
      >;
      const newTodo = await storage.addTodo(this.currentGoal.id, todo);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(newTodo, null, 2),
          },
        ],
      };
    }
  • Tool registration in ListTools response, including input schema definition for 'add_todo' matching Todo properties.
    {
      name: 'add_todo',
      description: 'Add a new todo item to the current plan',
      inputSchema: {
        type: 'object',
        properties: {
          title: {
            type: 'string',
            description: 'Title of the todo item',
          },
          description: {
            type: 'string',
            description: 'Detailed description of the todo item',
          },
          complexity: {
            type: 'number',
            description: 'Complexity score (0-10)',
            minimum: 0,
            maximum: 10,
          },
          codeExample: {
            type: 'string',
            description: 'Optional code example',
          },
        },
        required: ['title', 'description', 'complexity'],
      },
    },
  • TypeScript interface Todo defining the structure used for add_todo inputs and storage.
    export interface Todo {
      id: string;
      title: string;
      description: string;
      complexity: number;
      codeExample?: string;
      isComplete: boolean;
      createdAt: string;
      updatedAt: string;
    }
  • Storage helper function that implements the core logic: creates Todo with generated id/timestamps, appends to plan.todos, persists to JSON file.
    async addTodo(
      goalId: string,
      { title, description, complexity, codeExample }: Omit<Todo, 'id' | 'isComplete' | 'createdAt' | 'updatedAt'>
    ): Promise<Todo> {
      const plan = await this.getPlan(goalId);
      if (!plan) {
        throw new Error(`No plan found for goal ${goalId}`);
      }
    
      const todo: Todo = {
        id: Date.now().toString(),
        title,
        description,
        complexity,
        codeExample,
        isComplete: false,
        createdAt: new Date().toISOString(),
        updatedAt: new Date().toISOString(),
      };
    
      plan.todos.push(todo);
      plan.updatedAt = new Date().toISOString();
      await this.save();
      return todo;
    }
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 the basic action without disclosing behavioral traits. It doesn't mention permissions needed, whether the addition is reversible, how it affects the plan state, or any rate limits/constraints. For a mutation tool with zero annotation coverage, this is inadequate.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every part contributing essential information.

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 incomplete. It lacks details on behavioral aspects (e.g., side effects, error handling) and doesn't compensate for the missing structured data, making it insufficient for safe and effective use by an 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%, so the schema fully documents all parameters. The description adds no additional meaning beyond implying parameters relate to a 'todo item', which is already clear from the schema. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Add') and resource ('new todo item to the current plan'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'update_todo_status' or 'save_plan', which would require more specific language about creation versus modification.

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 like 'update_todo_status' or 'save_plan'. It mentions 'current plan' but doesn't clarify prerequisites (e.g., whether a plan must be active) or exclusions, leaving usage context implied rather than explicit.

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/PhilippMT/Software-planning-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server