Skip to main content
Glama
crazyrabbitLTC

Vibe-Coder MCP Server

start_feature_clarification

Clarify software feature requirements by generating structured specifications from initial descriptions, enabling clear development planning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureNameYes
initialDescriptionNo

Implementation Reference

  • The primary handler function that executes the logic for the 'start_feature_clarification' tool. It validates input, creates a new feature object, persists it, generates the first clarification question, and returns a response with the feature ID and question.
    /**
     * Start feature clarification handler
     */
    const startFeatureClarificationHandler: ToolHandler<z.infer<typeof StartFeatureClarificationSchema>> = async (params) => {
      try {
        const { featureName, initialDescription } = StartFeatureClarificationSchema.parse(params);
        
        // Create a new feature
        const feature = createFeatureObject(featureName, initialDescription);
        updateFeature(feature.id, feature);
        
        // Get the first clarification question
        const firstQuestion = getNextClarificationQuestion(feature);
        
        return {
          content: [{
            type: "text",
            text: `Feature ID: ${feature.id}\n\nLet's clarify your feature request. ${firstQuestion}`
          }]
        };
      } catch (error) {
        if (error instanceof z.ZodError) {
          const errorMessage = error.errors.map(e => `${e.path.join('.')}: ${e.message}`).join(', ');
          return createToolErrorResponse(`Validation error: ${errorMessage}`);
        }
        return createToolErrorResponse(error instanceof Error ? error.message : "Unknown error");
      }
    };
  • Zod schema defining the input parameters for the 'start_feature_clarification' tool: featureName (required string) and optional initialDescription.
    // Schema for start_feature_clarification
    const StartFeatureClarificationSchema = z.object({
      featureName: z.string().min(2).max(100),
      initialDescription: z.string().optional().default("")
    });
  • Registration of the 'start_feature_clarification' tool in the tool registry, specifying the handler, description, JSON schema for inputs, and example arguments.
    toolRegistry.register(
      'start_feature_clarification', 
      startFeatureClarificationHandler,
      'Start the clarification process for a new feature',
      {
        type: "object",
        properties: {
          featureName: {
            type: "string",
            description: "Name of the feature"
          },
          initialDescription: {
            type: "string",
            description: "Initial description of the feature"
          }
        },
        required: ["featureName"]
      },
      [
        {
          featureName: "User Authentication",
          initialDescription: "Add login and registration functionality to the application"
        },
        {
          featureName: "Data Export",
          initialDescription: "Allow users to export their data in CSV and JSON formats"
        }
      ]
    );
  • Direct registration of the 'start_feature_clarification' tool using the MCP server SDK, with inline Zod schema and simplified handler logic (appears to be a duplicate or alternative implementation).
    server.tool(
      "start_feature_clarification",
      { 
        featureName: z.string().min(2).max(100),
        initialDescription: z.string().optional().default("")
      },
      async ({ featureName, initialDescription }) => {
        // Create a new feature
        const feature = createFeatureObject(featureName, initialDescription);
        updateFeature(feature.id, feature);
        
        // Get the first clarification question
        const firstQuestion = getNextClarificationQuestion(feature);
        
        return {
          content: [{
            type: "text",
            text: `Feature ID: ${feature.id}\n\nLet's clarify your feature request. ${firstQuestion}`
          }]
        };
      }
    );
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