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 structured 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 designConfirmed function that executes the tool logic: confirms design phase completion, logs the event, and returns a markdown message advancing to task planning phase with session info.
    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`;
    }
  • The tool's input schema definition, including name, description, and required parameters (session_id, feature_name). Also serves as registration for the listTools endpoint.
    {
      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)
    The switch case in the MCP CallToolRequest handler that registers and dispatches to the designConfirmed implementation.
    case 'spec_coding_design_confirmed':
      result = await designConfirmed(args as any);
      break;
  • TypeScript interface defining the input parameters for the handler function, matching the MCP schema.
    export interface DesignConfirmedParams {
      session_id: string;
      feature_name: string;
    }
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 for behavioral disclosure. It mentions 'confirm' and 'proceed', suggesting a state transition or workflow step, but does not clarify if this is a read-only check, a mutation that updates status, what happens on failure, 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 directly states the tool's action. It is front-loaded with the core purpose and avoids unnecessary details, though it could be slightly more informative without losing conciseness.

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 of a workflow tool with no annotations and no output schema, the description is incomplete. It lacks details on what 'confirmation' entails, the expected outcome, error handling, or how it integrates with sibling tools, making it inadequate for an agent to use effectively without additional context.

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 schema description coverage is 100%, with both parameters ('session_id' and 'feature_name') documented in the schema. The description adds no additional meaning or context about the parameters beyond what the schema provides, such as how they relate to the confirmation process. This meets the baseline for high schema coverage.

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 a purpose ('Confirm the completion of the design document and proceed to the task planning phase'), which is clear but vague. It uses a verb ('Confirm') and resource ('design document'), but does not specify what 'confirm' entails or how it differs from sibling tools like 'spec_coding_design_start' or 'spec_coding_tasks_confirmed', making it less specific.

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 document completion and before task planning, but provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or comparisons to sibling tools, leaving the agent to infer context without clear direction.

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-driven-dev-mcp'

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