Structured Workflow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| refactor_workflowB | Start a structured refactoring workflow to improve existing code without changing functionality |
| create_feature_workflowC | Start a structured workflow for adding new functionality with integrated testing |
| test_workflowC | Start a focused workflow for writing or improving test coverage |
| tdd_workflowC | Start a Test-Driven Development workflow with Red-Green-Refactor cycles |
| build_custom_workflowA | Build a custom workflow with full control over phases and configuration. Use specific workflow tools (refactor_workflow, create_feature_workflow, etc.) for optimized presets. |
| setup_guidanceA | Get guidance for the SETUP phase - initialize workflow and establish patterns |
| audit_inventory_guidanceA | Get guidance for the AUDIT_INVENTORY phase - analyze code and catalog changes |
| compare_analyze_guidanceA | Get guidance for the COMPARE/ANALYZE phase - evaluating approaches |
| question_determine_guidanceC | Get guidance for the QUESTION_DETERMINE phase - clarify and finalize plan |
| refactor_guidanceB | Get guidance for the WRITE/REFACTOR phase - implementing changes |
| lint_guidanceA | Get guidance for the LINT phase - verifying code quality |
| iterate_guidanceA | Get guidance for the ITERATE phase - fixing issues |
| present_guidanceA | Get guidance for the PRESENT phase - summarizing work |
| test_guidanceA | Get MANDATORY guidance for the TEST phase - execute tests and validate functionality after refactoring |
| validate_actionC | Check if an action follows critical safety rules |
| validate_phase_completionC | Validate that current phase meets all completion requirements before allowing progression |
| user_input_required_guidanceA | Handle escalation to user input when iteration limits reached or checkpoints triggered |
| workflow_statusA | Check current workflow progress and session state |
| phase_outputA | Record the output/results when completing a workflow phase - REQUIRES ACTUAL OUTPUT ARTIFACTS with numbered file naming |
| discover_workflow_toolsA | List the workflow guidance tools provided by this MCP server |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Each tool targets a distinct phase or action, with clear guidance tools for specific workflow stages and separate workflow building tools. There is no overlap in purpose.
Most tools follow a 'verb_noun' or 'phase_guidance' pattern with underscores, but 'phase_output' deviates slightly. Overall, the naming is mostly consistent and predictable.
With 20 tools covering guidance for various phases, workflow stereotypes, validation, and status, the count is well-scoped for a workflow-oriented server.
The tool set comprehensively covers the full workflow lifecycle from setup through completion, including guidance for common phases, multiple workflow types, and validation checks.