[MCP] Patch working directory glitch

[notyashhh]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull Request Overview

This PR refines the MCP prompt flow and fixes a working-directory issue in the build utility.

• Streamlines and clarifies step-by-step instructions in mcpprompt.md
• Updates Autorest path references and placeholder syntax
• Adjusts generateAndBuild to use execSync with a cwd option instead of an inline cd

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
tools/Mcp/test/vscode/mcpprompt.md	Reorganized and cleaned up stage instructions; updated readme refs
tools/Mcp/src/services/utils.ts	Removed redundant inline cd, added cwd: workingDirectory to exec

Comments suppressed due to low confidence (1)

tools/Mcp/test/vscode/mcpprompt.md:77

• There's an extra '<' before 'specification'; it should be $(repo)/specification/<swaggerFileSpecs> so the input-file path resolves correctly.

  - $(repo)/<specification/<swaggerFileSpecs>

[VeryEarly]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).