You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Store the values for use in later steps like generating the README and executing Autorest.
24
-
- Once values are stored, mark Stage 1 as complete.
15
+
## Stage 1: Fuzzy selection and autorest inputs (reduced user input)
16
+
- Ask the user for only the approximate Azure service/module name (e.g., "hybrid connectivity").
17
+
- Call the MCP tool "list-spec-modules" to fetch all service folders from azure-rest-api-specs/specification.
18
+
- Fuzzily match the user's input to the closest service name. Show top 3 matches and ask the user to confirm the service folder to use.
19
+
- Call the MCP tool "list-providers" with the chosen service to retrieve provider namespaces. If multiple providers are returned, ask the user to pick one; if only one, select it automatically.
20
+
- Ask the user what they want to call the PowerShell module title/service-name (e.g., HybridConnectivity). This is the display/module name, not the spec folder name.
21
+
- Call the MCP tool "list-api-versions" with service and provider to get available versions, separated by Stable and Preview. Ask the user to choose stability (stable/preview) and a specific API version.
22
+
- Call the MCP tool "resolve-autorest-inputs" with service, provider, stability, and version to compute the 4 inputs: serviceName, commitId, serviceSpecs, swaggerFileSpecs.
23
+
- Store the resolved values for later steps (README generation and Autorest). Mark Stage 1 complete.
Copy file name to clipboardExpand all lines: tools/Mcp/src/specs/responses.json
+21-1Lines changed: 21 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,26 @@
29
29
"type": "tool",
30
30
"text": "Read examples from specs are under {0}. Implement empty test stubs under {1}. Test stubs are named as '.Test.ps1'. Define variables in function 'setupEnv' in 'utils.ps1' under {1}, and use these variables for test cases. Value of these variables are from {0}. Leave test cases as empty if you don't find any matches. You are expert in Azure-PowerShell and Autorest.PowerShell, You know how to map data from {0} to {1}. "
31
31
},
32
+
{
33
+
"name": "list-spec-modules",
34
+
"type": "tool",
35
+
"text": "Available modules under azure-rest-api-specs/specification: {0}"
0 commit comments