Skip to main content
Glama
kevinlin

Spec-driven Development MCP Server

by kevinlin

spec_coding_design_confirmed

Confirm design document completion and transition to task planning for spec-driven development workflows.

Instructions

Confirm the completion of the design document and proceed to the task planning phase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession identifier
feature_nameYesFeature name

Implementation Reference

  • The main handler function that executes the tool logic: confirms design completion for the feature, logs the event, and returns a markdown response with workflow progress and instructions to call the next tool.
    export async function designConfirmed(
      params: DesignConfirmedParams
    ): Promise<string> {
      const { session_id, feature_name } = params;
      console.error(`[MCP] Design confirmed for feature: ${feature_name}`);
      
      return `# āœ… Design Document Completed
    
    ## Generated Design Document:
    šŸ“„ "docs/specs/${feature_name}/design.md"
    
    The design document contains the complete technical architecture, component design, and implementation plan.
    
    ---
    
    ## Next Stage: Task Planning (4/5)
    
    ### Workflow Progress:
    - [x] 1. Goal Collection āœ…
    - [x] 2. Requirements Gathering āœ…
    - [x] 3. **Design Document** āœ…
    - [ ] 4. **Task Planning** ← Next Stage
    - [ ] 5. Task Execution
    
    Now please call \`spec_coding_tasks_start\` to begin the task planning stage.
    
    **Session Information**:
    - Session ID: \`${session_id}\`
    - Feature Name: \`${feature_name}\`
    - Requirements: āœ… Completed
    - Design: āœ… Completed`;
    }
  • JSON schema definition for the tool's input parameters: session_id and feature_name, provided in the list of tools.
    {
      name: 'spec_coding_design_confirmed',
      description: 'Confirm the completion of the design document and proceed to the task planning phase',
      inputSchema: {
        type: 'object',
        properties: {
          session_id: { 
            type: 'string', 
            description: 'Session identifier' 
          },
          feature_name: { 
            type: 'string', 
            description: 'Feature name' 
          }
        },
        required: ['session_id', 'feature_name']
      }
  • src/server.ts:227-229 (registration)
    Switch case in the CallToolRequest handler that routes calls to this tool name to the designConfirmed function.
    case 'spec_coding_design_confirmed':
      result = await designConfirmed(args as any);
      break;
  • TypeScript interface defining the expected parameters for the handler function, matching the JSON schema.
    export interface DesignConfirmedParams {
      session_id: string;
      feature_name: string;
    }
  • src/server.ts:11-11 (registration)
    Import statement that brings the handler function into the server module for use in tool dispatching.
    import { designConfirmed } from './tools/design_confirmed.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'proceed to the task planning phase,' suggesting a state transition, but doesn't disclose behavioral traits such as whether this is a read-only or mutating operation, what happens if the design isn't complete, or any side effects. This leaves significant gaps in understanding the tool's behavior.

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

Conciseness4/5

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

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for the tool's apparent complexity, though it could be more front-loaded with key details.

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 no annotations and no output schema, the description is incomplete. It lacks details on what 'confirming' entails, what the next phase involves, or any error conditions. For a tool that seems to manage workflow state transitions, more context is needed to understand its full role and effects.

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?

The input schema has 100% description coverage, with parameters 'session_id' and 'feature_name' clearly documented. The description adds no meaning beyond the schema, as it doesn't explain how these parameters relate to confirming design or task planning. Baseline 3 is appropriate since the schema does the heavy lifting.

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 confirms design completion and proceeds to task planning, which is a clear purpose. However, it doesn't specify what 'design document' refers to or how it distinguishes from sibling tools like spec_coding_design_start or spec_coding_tasks_confirmed, making it somewhat vague.

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 implies usage after design completion, but provides no explicit guidance on when to use this tool versus alternatives like spec_coding_tasks_start or spec_coding_tasks_confirmed. There are no exclusions or prerequisites mentioned, leaving usage unclear.

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