fix(nx-mcp): workspace tools shouldn't be available if cwd is not an nx workspace

[MaxKless]

falling back to the cwd as the workspace path is great but it should check for an nx workspace. Otherwise we will have a lot of nonfunctional tools.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 3a6dca1.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e-ci,ty...	✅ Succeeded	2m 59s	View ↗
nx-cloud record -- yarn nx-cloud conformance:check	✅ Succeeded	3s	View ↗
nx-cloud record -- yarn nx sync:check	✅ Succeeded	3s	View ↗
nx-cloud record -- ./gradlew :intellij:ktfmtCheck	✅ Succeeded	5s	View ↗
nx-cloud record -- ./gradlew projectReportAll	✅ Succeeded	3m 24s	View ↗
nx affected --targets=build,test,e2e-ci --confi...	✅ Succeeded	15m 50s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-06-02 09:27:20 UTC

[graphite-app]

The test description mentions a "non-existent path" but the test is actually checking a different directory path (/this/path/does/not/exist) than the one created in the setup (at join(e2eCwd, workspaceName)). This makes the test description accurate, but it might be clearer to rename this test suite from "with non-existent path" to something like "with command pointing to non-existent path" to better reflect that the test is validating behavior when the CLI is invoked with a path that doesn't exist, rather than testing from within a non-existent directory.

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.