Skip to main content
Glama
kingdomseed

Structured Workflow MCP

by kingdomseed

setup_guidance

Initialize workflows and establish structured patterns to enforce disciplined programming practices during the setup phase.

Instructions

Get guidance for the SETUP phase - initialize workflow and establish patterns

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Dispatch handler in the MCP tool call request processor that specifically handles the 'setup_guidance' tool by calling handlePhaseGuidance with the phase name and session manager.
    // Phase guidance tools (automatically route based on session configuration)
    case 'setup_guidance':
    case 'audit_inventory_guidance':
    case 'compare_analyze_guidance':
    case 'question_determine_guidance':
    case 'refactor_guidance':
    case 'lint_guidance':
    case 'iterate_guidance':
    case 'present_guidance':
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(await handlePhaseGuidance(name, sessionManager), null, 2)
        }]
      };
  • Tool schema definition including name, description, and empty input schema for setup_guidance.
    {
      name: 'setup_guidance',
      description: 'Get guidance for the SETUP phase - initialize workflow and establish patterns',
      inputSchema: { type: 'object', properties: {} }
    },
  • src/index.ts:144-147 (registration)
    Registration of phase guidance tools (including setup_guidance) into the main tools array provided to the MCP server.
    // Phase guidance tools
    ...createPhaseGuidanceTools(),                // Handles both suggestive and directive modes
    createTestGuidanceTool(),                     // TEST phase guidance
  • Primary handler function for phase guidance tools. For setup_guidance, determines if directive or suggestive mode and delegates to the appropriate guidance provider.
    export async function handlePhaseGuidance(
      phaseName: string,
      sessionManager: SessionManager
    ): Promise<PhaseGuidance> {
      const session = sessionManager.getSession();
      const isDirectiveMode = session?.workflowConfig !== undefined;
      
      // Route to appropriate guidance based on mode
      if (isDirectiveMode) {
        return getDirectiveGuidance(phaseName, sessionManager);
      } else {
        return getSuggestiveGuidance(phaseName, sessionManager);
      }
    }
  • Guidance data structure for setup_guidance in suggestive mode, containing phase objectives, instructions, suggested approach, notes, and expected outputs.
    setup_guidance: {
      phase: 'SETUP',
      objective: 'Initialize workflow environment and establish clear file organization patterns',
      instructions: [
        '--- ENVIRONMENT SETUP ---',
        'Verify your current working directory',
        'Understand the project structure and context',
        'Confirm available tools and capabilities',
        '--- FILE ORGANIZATION PATTERN ---',
        'Workflow outputs will be organized in: structured-workflow/{task-name}/',
        'This is the default location (customizable via --output-dir)',
        'All phase documents will use numbered prefixes: 00-setup, 01-audit, etc.',
        'Create your documentation content following this pattern'
      ],
      suggestedApproach: [
        'List your current working directory path',
        'Identify the main project files relevant to the task',
        'Document the default output pattern: structured-workflow/{task-name}/',
        'Confirm you understand where documentation will be created'
      ],
      importantNotes: [
        'This phase establishes the foundation for organized workflow execution',
        'The file pattern shown (structured-workflow/{task-name}/) is the expected location',
        'All subsequent phases will follow this numbered documentation pattern',
        'Understanding this pattern now prevents confusion later'
      ],
      expectedOutput: {
        workingDirectory: 'Current working directory path',
        projectContext: 'Brief description of the project',
        outputPattern: 'Confirmation of structured-workflow/{task-name}/ pattern',
        toolsAvailable: 'List of available analysis and file tools'
      },
      nextPhase: 'Use audit_inventory_guidance to begin analyzing the codebase'
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Get guidance' which suggests a read-only operation, but doesn't specify if this requires authentication, has side effects, or details about the guidance format (e.g., text, structured data). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 front-loads the core purpose ('Get guidance for the SETUP phase') and adds a clarifying goal ('initialize workflow and establish patterns'). There's no wasted text, making it appropriately sized for a simple tool, though it could be slightly more structured for better readability.

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 tool's complexity (simple with 0 parameters) but lack of annotations and no output schema, the description is incomplete. It doesn't explain what 'guidance' entails (e.g., format, content, or how it's delivered), which is critical for an agent to use it effectively. With many sibling tools, more context on output or usage scope would improve completeness.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, and the baseline for 0 parameters is 4, as it avoids unnecessary complexity while matching the schema's completeness.

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's purpose as 'Get guidance for the SETUP phase' with the goal to 'initialize workflow and establish patterns', which is clear but somewhat vague. It specifies a verb ('Get guidance') and resource ('SETUP phase'), but doesn't clearly differentiate from siblings like 'audit_inventory_guidance' or 'iterate_guidance' that might also provide guidance for different phases or aspects.

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 during the 'SETUP phase' but provides no explicit guidance on when to use this tool versus alternatives. With many sibling tools like 'build_custom_workflow' or 'discover_workflow_tools' that might overlap in initialization contexts, there's no mention of when-not-to-use or specific prerequisites, leaving the agent to guess based on phase alone.

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