Skip to main content
Glama
crazyrabbitLTC

Vibe-Coder MCP Server

add_task

Adds a task to a specific development phase, enabling structured workflow tracking for coding projects by defining feature requirements and implementation steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureIdYes
phaseIdYes
descriptionYes

Implementation Reference

  • Registration of the 'add_task' MCP tool, including inline input schema and execution handler function.
    server.tool(
      "add_task",
      {
        featureId: z.string().min(1),
        phaseId: z.string().min(1),
        description: z.string().min(1)
      },
      async ({ featureId, phaseId, description }) => {
        const feature = getFeature(featureId);
        if (!feature) {
          throw new Error(`Feature ${featureId} not found`);
        }
        
        const phase = feature.phases.find(p => p.id === phaseId);
        if (!phase) {
          throw new Error(`Phase ${phaseId} not found in feature ${featureId}`);
        }
        
        const task = addTaskDirectly(feature, phaseId, description);
        updateFeature(featureId, feature);
        
        // Debug log
        console.error(`DEBUG: Task created with ID: ${task.id}, type: ${typeof task.id}`);
        console.error(`DEBUG: Task object: ${JSON.stringify(task)}`);
        
        // Ensure task.id is explicitly converted to string and check if it's an object
        let taskId: string;
        
        if (typeof task.id === 'object') {
          taskId = JSON.stringify(task.id);
        } else {
          taskId = String(task.id);
        }
        
        return {
          content: [{
            type: "text",
            text: `Added task "${description.substring(0, 30)}${description.length > 30 ? '...' : ''}" with ID: ${taskId} to phase "${phase.name}"`
          }]
        };
      }
    );
  • Helper function used by the add_task handler to directly mutate the feature object by adding a new task to the specified phase.
    function addTaskDirectly(feature: Feature, phaseId: string, description: string): Task {
      const phase = feature.phases.find(p => p.id === phaseId);
      if (!phase) {
        throw new Error(`Phase ${phaseId} not found`);
      }
      
      const newTask = createTaskObject(description);
      
      // Convert task ID to string to ensure it's not an object
      if (typeof newTask.id !== 'string') {
        newTask.id = String(newTask.id);
      }
      
      phase.tasks.push(newTask);
      phase.updatedAt = now();
      feature.updatedAt = now();
      return newTask;
    }
  • Supporting function from phases module to add a task to a phase and persist via updateFeature. Similar logic to addTaskDirectly but returns updated feature.
    export function addTask(
      featureId: string,
      phaseId: string,
      description: string
    ): Feature | undefined {
      const feature = getFeature(featureId);
      if (!feature) return undefined;
      
      const phaseIndex = feature.phases.findIndex(p => p.id === phaseId);
      if (phaseIndex === -1) return undefined;
      
      const newTask = createTaskObject(description);
      
      const updatedPhases = [...feature.phases];
      updatedPhases[phaseIndex] = {
        ...updatedPhases[phaseIndex],
        tasks: [...updatedPhases[phaseIndex].tasks, newTask],
        updatedAt: now()
      };
      
      return updateFeature(featureId, { phases: updatedPhases });
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/crazyrabbitLTC/mcp-vibecoder'

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