Skip to main content
Glama

continue

Resume the execution of a paused Go program in the Delve debugger by specifying the debug session ID.

Instructions

Continue program execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the debug session

Implementation Reference

  • Core execution logic for the 'continue' tool: sends a delve 'continue' command to the debug session and returns a confirmation response.
    case "continue": { await sendDelveCommand(session, "Command", { name: "continue" }); return { content: [{ type: "text", text: "Continued execution" }] }; }
  • src/server.ts:181-194 (registration)
    Tool registration in ListToolsRequestSchema handler: defines name, description, and input schema for the 'continue' tool.
    { name: "continue", description: "Continue program execution", inputSchema: { type: "object", properties: { sessionId: { type: "string", description: "ID of the debug session" } }, required: ["sessionId"] } },
  • src/server.ts:410-413 (registration)
    Dispatch registration in CallToolRequestSchema handler: routes 'continue' calls to the control commands handler.
    // Control commands if (["setBreakpoint", "removeBreakpoint", "continue", "next", "step", "stepout", "variables", "evaluate"].includes(name)) { return handleControlCommands(name, args); }
  • Input schema definition for the 'continue' tool, specifying required 'sessionId' parameter.
    inputSchema: { type: "object", properties: { sessionId: { type: "string", description: "ID of the debug session" } }, required: ["sessionId"] }

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dwisiswant0/delve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server