updated old method as well

Author: notyashhh

tools/Mcp/test/vscode/mcpprompt.md

@@ -12,25 +12,33 @@
 
 # Instructions
 
-## Stage 1: Capturing Placeholder Values
-- Ask the user for the following placeholder values: serviceName, commitId, serviceSpecs, swaggerFileSpecs.
-  - Examples:
-    - serviceName: HybridConnectivity
-    - commitId: <commit hash of the swagger>
-    - serviceSpecs: hybridconnectivity/resource-manager
-    - swaggerFileSpecs: hybridconnectivity/resource-manager/Microsoft.HybridConnectivity/stable/2024-12-01/hybridconnectivity.json
-- Do not replace or modify this prompt file.
-- Store the values for use in later steps like generating the README and executing Autorest.
-- Once values are stored, mark Stage 1 as complete.
+## Stage 1: Interactive spec selection and autorest resolution
+- Ask the user for their desired **PowerShell module name** (e.g., "HybridConnectivity")
+- Call the MCP tool "list-spec-modules" to fetch all available specification folders from azure-rest-api-specs/specification.
+- From the full list, present 10 most relevant spec options to the user based on their PowerShell module name, or show a representative sample if no clear match.
+- Ask the user to choose which specification they want to use from the presented options, or ask if they want to see more options.
+- **Confirm the spec choice**: Once user selects a spec, ask them to confirm this is the correct specification for their needs (show the spec name clearly).
+- Call the MCP tool "list-providers" with the chosen spec folder to retrieve available provider namespaces.
+- Present the list of providers to the user:
+  - If multiple providers are returned, ask the user to pick one
+  - If only one provider exists, select it automatically but confirm with the user
+- **Confirm the provider choice**: Ask the user to confirm this is the correct provider namespace.
+- Call the MCP tool "list-api-versions" with the chosen spec folder and provider to get available versions, separated by Stable and Preview.
+- Present the API version options to the user and ask them to choose:
+  1. **Stability**: stable or preview
+  2. **API version**: specific version from the available list
+- **Confirm the API version choice**: Ask the user to confirm their stability and version selection.
+- Call the MCP tool "resolve-autorest-inputs" with the chosen spec folder, provider, stability, and version to compute the 4 autorest inputs: serviceName, commitId, serviceSpecs, swaggerFileSpecs.
+- Store the resolved values for later steps (README generation and Autorest). Mark Stage 1 complete.
 
 ## Stage 2: Generating partner powershell module
 - FOLLOW ALL THE STEPS. DO NOT SKIP ANY STEPS.
 - Navigate to the `src` folder in the home "azure-powershell" directory.
-- Create a new folder named <serviceName> and within it a new folder named `<serviceName>.Autorest`. (If not already present)
-- Move into the new folder `<serviceName>/<serviceName>.Autorest`, using the command `cd <serviceName>/<serviceName>.Autorest`.
+- Create a new folder named <PowerShell module name> and within it a new folder named `<PowerShell module name>.Autorest`. (If not already present)
+- Move into the new folder `<PowerShell module name>/<PowerShell module name>.Autorest`, using the command `cd <PowerShell module name>/<PowerShell module name>.Autorest`.
 - Create a new file `README.md`. (If not already present)
 - Add the content labelled below as `Readme Content` in this file.
-- Use the "generate-autorest" mcp tool to generate the <serviceName> module.
+- Use the "generate-autorest" mcp tool to generate the <PowerShell module name> module.
 - Stage 2 Complete.
 
 ## Stage 3: Updating Example Files
@@ -78,8 +86,8 @@ input-file:
 
 module-version: 0.1.0 
 
-title: <serviceName> 
-service-name: <serviceName> 
+title: <PowerShell module name> 
+service-name: <PowerShell module name> 
 subject-prefix: $(service-name) 
 
 directive: