next
Step to the next line in a Go program debug session using the Delve debugger. Provide the session ID to continue debugging and analyze code progression effectively.
Instructions
Step over to next line
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sessionId | Yes | ID of the debug session |
Implementation Reference
- src/handlers/control.ts:62-70 (handler)The core implementation of the "next" MCP tool handler. It sends a "next" command to the active Delve debug session and returns a confirmation message.case "next": { await sendDelveCommand(session, "Command", { name: "next" }); return { content: [{ type: "text", text: "Stepped to next line" }] }; }
- src/server.ts:198-207 (schema)Input schema definition for the "next" tool, requiring a sessionId.inputSchema: { type: "object", properties: { sessionId: { type: "string", description: "ID of the debug session" } }, required: ["sessionId"] }
- src/server.ts:195-208 (registration)Registration of the "next" tool in the ListToolsRequestSchema response, including name, description, and schema.{ name: "next", description: "Step over to next line", inputSchema: { type: "object", properties: { sessionId: { type: "string", description: "ID of the debug session" } }, required: ["sessionId"] } },
- src/server.ts:410-413 (registration)Dispatch/registration logic in CallToolRequestSchema handler that routes the "next" tool call to handleControlCommands.// Control commands if (["setBreakpoint", "removeBreakpoint", "continue", "next", "step", "stepout", "variables", "evaluate"].includes(name)) { return handleControlCommands(name, args); }