Skip to content

Commit 6c796b4

Browse files
committed
Updated return Spec
1 parent 8a16ffe commit 6c796b4

File tree

4 files changed

+8
-14
lines changed

4 files changed

+8
-14
lines changed

tools/Mcp/src/services/toolsService.ts

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -316,18 +316,7 @@ export class ToolsService {
316316
// Write README.md file
317317
await utils.writeFileIfNotExists(readmePath, readmeContent);
318318

319-
return [
320-
selectedService,
321-
selectedProvider,
322-
selectedVersion,
323-
selectedStability,
324-
resolved.serviceName,
325-
resolved.commitId,
326-
resolved.serviceSpecs,
327-
resolved.swaggerFileSpecs,
328-
moduleName,
329-
autorestPath
330-
];
319+
return [moduleName];
331320

332321
} catch (error) {
333322
const errorMessage = error instanceof Error ? error.message : String(error);

tools/Mcp/src/specs/prompts/partner-module-workflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525

2626
## Stage 2: Generating partner powershell module
2727
- FOLLOW ALL THE STEPS. DO NOT SKIP ANY STEPS.
28-
- Navigate to the newly created module directory (should be under `src/<PowerShell module name>/<PowerShell module name>.Autorest`)
28+
- Navigate to the created module directory, you can find this from the input given by the user using ellicitation for the input "moduleName" (should be under `src/<PowerShell module name>/<PowerShell module name>.Autorest`)
2929
- Use the "generate-autorest" mcp tool to generate the <PowerShell module name> module using the README.md that was created by setupModuleStructure
3030
- Stage 2 Complete.
3131

tools/Mcp/src/specs/responses.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,11 @@
2929
"type": "tool",
3030
"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}. "
3131
},
32+
{
33+
"name": "setup-module-structure",
34+
"type": "tool",
35+
"text": "Created the module structure under the folder: {0}."
36+
},
3237
{
3338
"name": "create-greeting",
3439
"type": "prompt",

tools/Mcp/src/specs/specs.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@
7373
"callbackName": "createTestsFromSpecs"
7474
},
7575
{
76-
"name": "setupModuleStructure",
76+
"name": "setup-module-structure",
7777
"description": "Setup Azure PowerShell module structure by selecting service, provider, and API version through interactive dropdowns",
7878
"parameters": [],
7979
"callbackName": "setupModuleStructure"

0 commit comments

Comments
 (0)