Remove old tool names

Author: CapulusCodeNinja

README.md

@@ -114,15 +114,15 @@ Architecture, testing, contribution guide
 ## 🛠 Available Tools (8 tools)
 
 ### Windows Debugging Tools
-- **Crash Dump Analysis**: `nexus_open_dump`, `nexus_close_dump`
+- **Crash Dump Analysis**: `nexus_open_dump_analyze_session`, `nexus_close_dump_analyze_session`
 - **Remote Debugging**: `nexus_start_remote_debug`, `nexus_stop_remote_debug`  
-- **Async Command Queue**: `nexus_exec_debugger_command_async`, `nexus_debugger_command_status`, `nexus_debugger_command_cancel`, `nexus_list_debugger_commands`
+- **Async Command Queue**: `nexus_dump_analyze_session_async_command`, `nexus_dump_analyze_session_async_command_status`, `nexus_debugger_command_cancel`, `nexus_list_debugger_commands`
 
 **🔄 Async Workflow with Notifications:**
 ```bash
-1. nexus_exec_debugger_command_async → Returns commandId
+1. nexus_dump_analyze_session_async_command → Returns commandId
 2. Listen for notifications/commandStatus → Real-time progress
-3. OR poll nexus_debugger_command_status → Get results
+3. OR poll nexus_dump_analyze_session_async_command_status → Get results
 ```
 
 > 📖 **Complete tool reference with examples:** **[📋 TOOLS.md](docs/TOOLS.md)**

TEST_NOTIFICATIONS.md

@@ -32,7 +32,7 @@ The test output above shows **exactly** what you'll see in your MCP server logs
        id = 1
        method = "tools/call"
        params = @{
-           name = "nexus_open_dump"
+           name = "nexus_open_dump_analyze_session"
            arguments = @{
                dumpPath = "/mnt/c/inetpub/wwwroot/uploads/test_dump.dmp"
                symbolsPath = "/mnt/d/symbols"
@@ -54,7 +54,7 @@ The test output above shows **exactly** what you'll see in your MCP server logs
    "Please analyze the crash dump at /mnt/c/inetpub/wwwroot/uploads/dump_20250925_112751.dmp using symbols from /mnt/d/symbols"
    ```
 
-3. **Watch your MCP server console** - you'll see the conversion notifications when the AI calls `nexus_open_dump`
+3. **Watch your MCP server console** - you'll see the conversion notifications when the AI calls `nexus_open_dump_analyze_session`
 
 ### Method 3: Direct Stdio Testing
 
@@ -65,7 +65,7 @@ The test output above shows **exactly** what you'll see in your MCP server logs
 
 2. **Send JSON-RPC directly** (paste this and press Enter):
    ```json
-   {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"nexus_open_dump","arguments":{"dumpPath":"/mnt/c/inetpub/wwwroot/uploads/test_dump.dmp","symbolsPath":"/mnt/d/symbols"}}}
+   {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"nexus_open_dump_analyze_session","arguments":{"dumpPath":"/mnt/c/inetpub/wwwroot/uploads/test_dump.dmp","symbolsPath":"/mnt/d/symbols"}}}
    ```
 
 3. **See the logs in real-time** on the console

docs/TOOLS.md

@@ -7,32 +7,32 @@
 Windows debugging capabilities through WinDBG/CDB integration:
 
 ### Core Debugging Commands
-- **Crash Dump Analysis**: `nexus_open_dump`, `nexus_close_dump`
+- **Crash Dump Analysis**: `nexus_open_dump_analyze_session`, `nexus_close_dump_analyze_session`
 - **Remote Debugging**: `nexus_start_remote_debug`, `nexus_stop_remote_debug`  
-- **Command Execution**: `nexus_exec_debugger_command_async` (🔄 ASYNC QUEUE: Always returns commandId, use `nexus_debugger_command_status` for results)
-- **Queue Management**: `nexus_debugger_command_status`, `nexus_debugger_command_cancel`, `nexus_list_debugger_commands`
+- **Command Execution**: `nexus_dump_analyze_session_async_command` (🔄 ASYNC QUEUE: Always returns commandId, use `nexus_dump_analyze_session_async_command_status` for results)
+- **Queue Management**: `nexus_dump_analyze_session_async_command_status`, `nexus_debugger_command_cancel`, `nexus_list_debugger_commands`
 
 ### 🔄 Async Command Execution Workflow
 
 **IMPORTANT**: All WinDBG commands use an async queue system with real-time notifications:
 
 ```bash
-1. Call nexus_exec_debugger_command_async {"command": "!analyze -v"}
+1. Call nexus_dump_analyze_session_async_command {"command": "!analyze -v"}
    → Returns: {"commandId": "abc-123", "status": "queued", ...}
 
 2. Listen for real-time notifications:
    → notifications/commandStatus: {"status": "executing", "progress": 25, ...}
    → notifications/commandHeartbeat: {"elapsed": "30s", ...} (for long commands)
    → notifications/commandStatus: {"status": "completed", "result": "ACTUAL_OUTPUT"}
 
-3. OR poll nexus_debugger_command_status {"commandId": "abc-123"}  
+3. OR poll nexus_dump_analyze_session_async_command_status {"commandId": "abc-123"}  
    → Returns: {"status": "executing", ...} (keep polling)
    → Returns: {"status": "completed", "result": "ACTUAL_OUTPUT"}
 
 4. Extract the "result" field for your WinDBG command output
 ```
 
-**⚠️ CRITICAL**: `nexus_exec_debugger_command_async` NEVER returns command results directly. You MUST use `nexus_debugger_command_status` to get results or listen for notifications!
+**⚠️ CRITICAL**: `nexus_dump_analyze_session_async_command` NEVER returns command results directly. You MUST use `nexus_dump_analyze_session_async_command_status` to get results or listen for notifications!
 
 ## 📡 Real-Time Notifications
 

mcp_nexus/Models/McpModels.cs

@@ -123,7 +123,7 @@ public class McpServerDetails
             "Provides asynchronous debugging commands with live status updates via server-initiated notifications. " +
             "Supports notifications/commandStatus (execution progress), notifications/commandHeartbeat (long-running command updates), " +
             "notifications/sessionRecovery (debugging session recovery), notifications/serverHealth (server status), " +
-            "and standard MCP notifications/tools/list_changed. All commands execute asynchronously - use nexus_debugger_command_status() " +
+            "and standard MCP notifications/tools/list_changed. All commands execute asynchronously - use nexus_dump_analyze_session_async_command_status() " +
             "to get results and monitor for real-time notifications about execution progress.";
     }
 

mcp_nexus/Session/ThreadSafeSessionManager.cs

@@ -463,7 +463,7 @@ private List<string> GenerateUsageHints(SessionInfo session, List<(string Id, st
                 hints.Add("⏰ Session has been inactive - will auto-expire if no activity");
             }
 
-            hints.Add($"📊 Use nexus_debugger_command_status to check command results");
+            hints.Add($"📊 Use nexus_dump_analyze_session_async_command_status to check command results");
             hints.Add($"🎯 Always include sessionId='{session.SessionId}' in your requests");
 
             return hints;

mcp_nexus_tests/Manual/PathConversionDemo.cs

@@ -58,7 +58,7 @@ public void DemonstratePathConversion()
 
             output.WriteLine("=== How to see this in real MCP server usage ===");
             output.WriteLine("1. Start MCP server: dotnet run --project mcp_nexus -- --http");
-            output.WriteLine("2. Call nexus_open_dump with WSL paths");
+            output.WriteLine("2. Call nexus_open_dump_analyze_session with WSL paths");
             output.WriteLine("3. Check server console output for conversion log messages");
             output.WriteLine("4. Look for lines containing 'Converted WSL path'");
         }
@@ -73,7 +73,7 @@ public void SimulateActualMcpServerLogging()
             var originalDumpPath = "/mnt/c/inetpub/wwwroot/uploads/dump_20250925_112751.dmp";
             var dumpPath = PathHandler.NormalizeForWindows(originalDumpPath);
 
-            output.WriteLine($"AI calls nexus_open_dump with:");
+            output.WriteLine($"AI calls nexus_open_dump_analyze_session with:");
             output.WriteLine($"  dumpPath: \"{originalDumpPath}\"");
             output.WriteLine("");
 

mcp_nexus_web/crash-analyze-command.md

@@ -26,14 +26,14 @@ The following steps must be performed sequentially. Ensure all mandatory rules a
 
 1.  **Confirm MCP servers:** Confirm MCP servers are available
 2.  **List available MCP Tools:** List all the available MCP servers and there tools
-3.  **Verify MCP Tools:** Verify that `nexus_open_dump`, `nexus_close_dump` and `nexus_exec_debugger_command_async` is available in your tool list
+3.  **Verify MCP Tools:** Verify that `nexus_open_dump_analyze_session`, `nexus_close_dump_analyze_session` and `nexus_dump_analyze_session_async_command` is available in your tool list
 4.  **Analyze issue** In case the verification fails elaborate what the issue might be as the server is set in the global mcp.json of the user account `droller`. Check the configuration file and test the connection.
 
 ### 🔧 **REQUIRED ACTIONS & WORKFLOW**
 
 The following steps must be performed sequentially. Ensure all mandatory rules are followed at each stage.
 
-1.  **Initialize Analysis:** Open the dump file with the tool from Nexus MCP server `mcp_nexus_open_dump`
+1.  **Initialize Analysis:** Open the dump file with the tool from Nexus MCP server `nexus_open_dump_analyze_session`
 2.  **Source Code Retrieval:**
     * Set the source server path: `.srcpath srv\*[workingdir]\source`
     * Enable source verbosity: `.srcnoisy 3`