Skip to main content
Glama
kingdomseed

Structured Workflow MCP

by kingdomseed

create_feature_workflow

Start a structured workflow to add new functionality with integrated testing, ensuring disciplined development practices through verification at each phase.

Instructions

Start a structured workflow for adding new functionality with integrated testing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesDescription of the feature to create
contextNoAdditional context (optional)

Implementation Reference

  • The handler function that executes the create_feature_workflow tool. It calls executeWorkflow with workflowType set to 'feature' and passes the task and context.
    export async function handleCreateFeatureWorkflow(
      params: { task: string; context?: any },
      sessionManager: SessionManager
    ) {
      return executeWorkflow(
        {
          task: params.task,
          workflowType: 'feature',
          context: params.context
        },
        sessionManager
      );
    }
  • The input schema defining the parameters for the create_feature_workflow tool, including required 'task' and optional 'context'.
    inputSchema: {
      type: 'object',
      properties: {
        task: {
          type: 'string',
          description: 'Description of the feature to create'
        },
        context: {
          type: 'object',
          description: 'Additional context (optional)',
          properties: {
            targetFiles: { 
              type: 'array', 
              items: { type: 'string' },
              description: 'Files where the feature will be added'
            },
            scope: { 
              type: 'string', 
              enum: ['file', 'directory', 'project'],
              description: 'The scope of the feature'
            },
            requirements: { 
              type: 'array', 
              items: { type: 'string' },
              description: 'Feature requirements and acceptance criteria'
            }
          }
        }
      },
      required: ['task']
    }
  • src/index.ts:137-157 (registration)
    Registration of the tool in the server's tools list by including createFeatureWorkflowTool() in the tools array used for ListToolsRequestHandler.
    const tools = [
      // Workflow entry points
      createRefactorWorkflowTool(),                 // Refactoring workflow
      createFeatureWorkflowTool(),                  // Feature creation workflow
      createTestWorkflowTool(),                     // Test writing workflow
      createTddWorkflowTool(),                      // TDD workflow
      createBuildCustomWorkflowTool(),              // Custom workflow builder
      
      // Phase guidance tools
      ...createPhaseGuidanceTools(),                // Handles both suggestive and directive modes
      createTestGuidanceTool(),                     // TEST phase guidance
      
      // Validation tools
      ...createValidationTools(),                   // Both validate_action and validate_phase_completion
      
      // Workflow management
      createUserInputRequiredTool(),                // Escalation handling
      createWorkflowStatusTool(),                   // Workflow status
      createPhaseOutputTool(),                      // Phase output recording
      createDiscoverWorkflowToolsTool()             // Tool discovery
    ];
  • src/index.ts:234-240 (registration)
    Dispatch handler in the CallToolRequestSchema that routes calls to 'create_feature_workflow' to the handleCreateFeatureWorkflow function.
    case 'create_feature_workflow':
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(await handleCreateFeatureWorkflow(args as any, sessionManager), null, 2)
        }]
      };
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. While 'start a structured workflow' implies an initiation action, it doesn't describe what the workflow entails, whether it's interactive or automated, what permissions are needed, what happens after starting, or what the expected outcome is. This leaves significant behavioral gaps for a tool that presumably creates something.

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 gets straight to the point with no wasted words. It's appropriately sized for what it communicates and is well-structured for quick comprehension.

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?

For a tool that presumably creates workflows (a potentially complex operation), the description is insufficient. With no annotations, no output schema, and many sibling tools, it should explain more about what 'structured workflow' means, what 'integrated testing' entails, and how this differs from other workflow tools. The current description leaves too many contextual questions unanswered.

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 description provides no parameter information whatsoever, but the input schema has 100% description coverage, thoroughly documenting both the 'task' parameter and the nested 'context' object with its sub-properties. This meets the baseline of 3 since the schema does the heavy lifting, though the description adds no value beyond what's already in the structured schema.

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

Purpose4/5

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

The description clearly states the action ('start a structured workflow') and the purpose ('for adding new functionality with integrated testing'), which is specific and actionable. However, it doesn't explicitly differentiate this tool from its many siblings like 'build_custom_workflow' or 'tdd_workflow', which appear related to workflow creation.

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 provides no guidance on when to use this tool versus alternatives. With 18 sibling tools including several workflow-related ones (e.g., 'build_custom_workflow', 'tdd_workflow', 'test_workflow'), there's no indication of what makes this tool distinct or when it's the appropriate choice.

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/kingdomseed/structured-workflow-mcp'

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