step_into
Step into function calls while debugging NodeJS applications to inspect variables and trace execution flow within the MCP NodeJS Debugger.
Instructions
Steps into function calls
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- src/mcp-server.js:661-693 (handler)The handler function for the 'step_into' tool. It checks if the debugger is enabled and paused, then sends the 'Debugger.stepInto' command to the inspector, or returns appropriate error messages.async () => { try { // Ensure debugger is enabled if (!inspector.debuggerEnabled) { await inspector.enableDebugger(); } if (!inspector.paused) { return { content: [{ type: "text", text: "Debugger is not paused at a breakpoint" }] }; } await inspector.send('Debugger.stepInto', {}); return { content: [{ type: "text", text: "Stepped into function call" }] }; } catch (err) { return { content: [{ type: "text", text: `Error stepping into: ${err.message}` }] }; } }
- src/mcp-server.js:657-694 (registration)Registration of the 'step_into' MCP tool using server.tool, including empty input schema and the handler function.server.tool( "step_into", "Steps into function calls", {}, async () => { try { // Ensure debugger is enabled if (!inspector.debuggerEnabled) { await inspector.enableDebugger(); } if (!inspector.paused) { return { content: [{ type: "text", text: "Debugger is not paused at a breakpoint" }] }; } await inspector.send('Debugger.stepInto', {}); return { content: [{ type: "text", text: "Stepped into function call" }] }; } catch (err) { return { content: [{ type: "text", text: `Error stepping into: ${err.message}` }] }; } } );