Skip to main content
Glama
crazyrabbitLTC

Vibe-Coder MCP Server

create_phase

Adds an implementation phase to a coding feature by specifying its name, description, and feature ID for structured workflow tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureIdYes
nameYes
descriptionYes

Implementation Reference

  • The main handler function for the 'create_phase' MCP tool. It retrieves the feature, creates a new phase using the helper function, updates the feature in storage, and returns a success message with the new phase ID.
    async ({ featureId, name, description }) => {
      const feature = getFeature(featureId);
      if (!feature) {
        throw new Error(`Feature ${featureId} not found`);
      }
      
      const phase = createPhaseDirectly(feature, name, description);
      updateFeature(featureId, feature);
      
      return {
        content: [{
          type: "text",
          text: `Created phase "${name}" with ID ${phase.id} for feature "${feature.name}"`
        }]
      };
    }
  • Zod input schema validation for the 'create_phase' tool parameters: featureId, name, and description.
    {
      featureId: z.string().min(1),
      name: z.string().min(1),
      description: z.string().min(1)
    },
  • Registration of the 'create_phase' tool on the MCP server instance using server.tool(), including inline schema and handler.
    server.tool(
      "create_phase",
      {
        featureId: z.string().min(1),
        name: z.string().min(1),
        description: z.string().min(1)
      },
      async ({ featureId, name, description }) => {
        const feature = getFeature(featureId);
        if (!feature) {
          throw new Error(`Feature ${featureId} not found`);
        }
        
        const phase = createPhaseDirectly(feature, name, description);
        updateFeature(featureId, feature);
        
        return {
          content: [{
            type: "text",
            text: `Created phase "${name}" with ID ${phase.id} for feature "${feature.name}"`
          }]
        };
      }
    );
  • Helper function called by the create_phase handler to create and append a new Phase object to the feature's phases array.
    function createPhaseDirectly(feature: Feature, name: string, description: string): Phase {
      const newPhase = createPhaseObject(name, description);
      feature.phases.push(newPhase);
      feature.updatedAt = new Date();
      return newPhase;
    }
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