Skip to main content
Glama
kingdomseed

Structured Workflow MCP

by kingdomseed

iterate_guidance

Provides structured guidance for fixing issues during the ITERATE phase of development workflows, helping enforce disciplined programming practices through verified outputs.

Instructions

Get guidance for the ITERATE phase - fixing issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the tool schema (name, description, inputSchema) for 'iterate_guidance' as part of createPhaseGuidanceTools().
    {
      name: 'iterate_guidance',
      description: 'Get guidance for the ITERATE phase - fixing issues',
      inputSchema: { type: 'object', properties: {} }
    },
  • src/index.ts:145-147 (registration)
    Registers the phase guidance tools, including 'iterate_guidance', by spreading the array from createPhaseGuidanceTools().
    // Phase guidance tools
    ...createPhaseGuidanceTools(),                // Handles both suggestive and directive modes
    createTestGuidanceTool(),                     // TEST phase guidance
  • Switch case dispatcher that handles 'iterate_guidance' tool calls by invoking the shared handlePhaseGuidance function.
    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)
        }]
      };
  • Core handler function for all phase guidance tools, including 'iterate_guidance'. Determines mode (directive/suggestive) and delegates to appropriate guidance generator.
    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);
      }
    }
  • Suggestive mode guidance configuration for ITERATE phase, providing instructions, approach, expected output, and next steps.
    iterate_guidance: {
      phase: 'ITERATE',
      objective: 'Fix issues discovered during the LINT phase',
      instructions: [
        'Address errors first, then warnings',
        'Fix one issue at a time',
        'Re-run linters after each fix',
        'Don\'t introduce new issues while fixing',
        'Document what you changed and why'
      ],
      suggestedApproach: [
        'Start with syntax/type errors',
        'Then fix logical errors',
        'Address style issues last',
        'Test after each significant fix',
        'Consider if the fix reveals a design issue'
      ],
      expectedOutput: {
        fixesApplied: 'List of all fixes made',
        fixDescription: 'What each fix addressed',
        remainingIssues: 'Any issues you couldn\'t fix',
        verificationStatus: 'Results after fixes',
        lessonsLearned: 'Insights from the issues found'
      },
      nextPhase: 'Re-run lint_guidance or proceed to present_guidance when clean'
    },
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' but does not clarify what form the guidance takes (e.g., text, steps, examples), whether it's static or dynamic, or any operational constraints like permissions or rate limits. This leaves significant gaps for a tool with zero annotation coverage.

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 purpose without unnecessary words. It is front-loaded and appropriately sized for a no-parameter tool, 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 lack of annotations and output schema, the description is incomplete for a guidance tool. It does not explain what the guidance output looks like, how it's structured, or any behavioral traits, leaving the agent with insufficient information to understand the tool's full context and usage.

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 no parameter information is needed in the description. The description does not add any parameter details, which is appropriate, earning a baseline score of 4 for not introducing confusion or redundancy.

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 ITERATE phase - fixing issues', which identifies a verb ('Get guidance') and resource ('ITERATE phase'), but lacks specificity about what 'guidance' entails or how it differs from similar sibling tools like 'refactor_guidance' or 'test_guidance'. It is not tautological but remains vague in scope.

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 'ITERATE phase' for 'fixing issues', but provides no explicit guidance on when to use this tool versus alternatives like 'refactor_guidance' or 'test_guidance', nor any prerequisites or exclusions. It offers minimal context without clear differentiation from siblings.

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