Some of the MCP server commands modify files on disk directly, so if there are unsaved changes you can result in conflicts when trying to save:

We previously excluded the run_tests tool in the MCP server (#5639) because VS Code contributes a version that works better inside the editor. I wonder if we should do something similar here:

• Identify any commands that might modify directly on disk
• Ensure Dart-Code (or VS Code) exposes the equivalent command directly
• Hide the MCP version of the tool

We should try to avoid duplicating functionality that we don't already have and is in the MCP server, but for things like format where we already have implementations but they're just not exposed to the model, maybe it makes sense to just expose them?

We'd need to review the full set and agree which this makes sense for.

WDYT @jakemac53?