Skip to main content
Glama
kevinlin

Spec-driven Development MCP Server

by kevinlin

spec_coding_workflow_start

Start a spec-driven development workflow to transform ideas into implementation by initiating the goal collection phase.

Instructions

Start the specs workflow and begin the goal collection phase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that implements the tool logic: generates a unique session ID, loads the 'ask-goal.md' template, and returns a formatted markdown message starting the workflow with instructions for the goal collection phase.
    export async function workflowStart(): Promise<string> {
      const session_id = generateSessionId();
      console.error(`[MCP] Starting workflow with session_id: ${session_id}`);
      
      // Use ask-goal.md template
      const template = await readTemplate('ask-goal.md', {
        session_id
      });
      
      return `# 🚀 Spec-driven Development Workflow Started
    
    ## Current Stage: Goal Collection (1/5)
    
    Welcome to the Spec-driven development workflow! I'll help you complete the entire development process from requirements to code.
    
    ### Workflow Overview:
    - [ ] 1. **Goal Collection** ← Current Stage
    - [ ] 2. Requirements Gathering
    - [ ] 3. Design Documentation
    - [ ] 4. Task Planning
    - [ ] 5. Task Execution
    
    ---
    
    ${template}
    
    ---
    
    **Session Information**:
    - Session ID: \`${session_id}\`
    
    **Important**:
    - Please discuss the feature goals with me thoroughly until the goals are completely clear
    - **Only when you explicitly confirm the goals can you call** \`spec_coding_goal_confirmed\` tool
    - **Never** call the next stage tool before the user **explicitly confirms the goals**`;
    }
  • Tool specification including name, description, and input schema (empty object, no required parameters). This is returned by the ListTools handler.
    {
      name: 'spec_coding_workflow_start',
      description: 'Start the specs workflow and begin the goal collection phase',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • src/server.ts:207-208 (registration)
    Dispatches the tool call to the workflowStart handler function in the MCP CallToolRequest switch statement.
    case 'spec_coding_workflow_start':
      result = await workflowStart();
  • Workflow step definition that references this tool as the starting point of the overall spec-coding workflow.
    {
      step_number: 1,
      name: STEP_NAMES.GOAL_CONFIRMATION,
      description: 'Clarify the feature development goal through conversation',
      tool: 'spec_coding_workflow_start → spec_coding_goal_confirmed',
      deliverable: 'Clear feature goal and feature_name'
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions starting a workflow and beginning goal collection, but doesn't describe what this entails—such as whether it initiates a multi-step process, requires user input, has side effects, or returns any data. For a tool with zero annotation coverage, this is insufficient to understand its behavior.

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 any wasted words. It is front-loaded with the core action ('Start the specs workflow'), making it easy to parse and understand quickly.

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 the complexity implied by sibling tools (e.g., multiple phases like design, requirements, tasks), the description is incomplete. It lacks details on what the workflow entails, how it interacts with other tools, or what happens after starting. With no annotations and no output schema, the agent is left with minimal context to use this tool effectively.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter details, which is appropriate since there are none. A baseline of 4 is applied as it correctly avoids unnecessary parameter information.

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

Purpose3/5

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

The description states the tool 'Start[s] the specs workflow and begin[s] the goal collection phase', which provides a clear action ('Start') and target ('specs workflow'). However, it doesn't distinguish this from sibling tools like 'spec_coding_design_start' or 'spec_coding_requirements_start', leaving ambiguity about what makes this specific workflow initiation different.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description implies it's for starting a workflow and beginning goal collection, but it doesn't specify prerequisites, when to choose it over other start tools (e.g., 'spec_coding_design_start'), or what context triggers its use. This leaves the agent without clear usage instructions.

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/kevinlin/spec-coding-mcp'

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