Skip to main content
Glama

continue

Resume execution of a paused Go program within an active debug session by specifying the session ID.

Instructions

Continue program execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the debug session

Implementation Reference

  • Handler for the 'continue' tool - sends a 'Command' with name 'continue' to the Delve debugger to resume program execution.
    case "continue": {
      await sendDelveCommand(session, "Command", { name: "continue" });
      return {
        content: [{
          type: "text",
          text: "Continued execution"
        }]
      };
    }
  • Schema/tool definition for 'continue' - defines its name, description, and input schema (requires sessionId).
    {
      name: "continue",
      description: "Continue program execution",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: {
            type: "string",
            description: "ID of the debug session"
          }
        },
        required: ["sessionId"]
      }
    },
  • src/server.ts:411-413 (registration)
    Registration/route for 'continue' - the CallToolRequestSchema handler routes the 'continue' tool name to handleControlCommands.
    if (["setBreakpoint", "removeBreakpoint", "continue", "next", "step", "stepout", "variables", "evaluate"].includes(name)) {
      return handleControlCommands(name, args);
    }
  • Imports the helper sendDelveCommand which is used by the continue handler to communicate with the Delve debugger.
    import { sessions, sendDelveCommand } from '../session.js';
    import { Breakpoint } from '../types.js';
    
    /**
     * Handle execution control commands
     */
    export async function handleControlCommands(name: string, args: any) {
      const { sessionId } = args;
      const session = sessions.get(sessionId);
      if (!session) {
        throw new Error(`Debug session ${sessionId} not found`);
      }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'continue program execution' without clarifying side effects, safety, or what happens after continuation (e.g., pause on next breakpoint).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise at three words, but it sacrifices informativeness. It earns its place as a minimal viable description, but could include more context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with only one parameter, but the description lacks context about when to use it, what happens after invocation, and there is no output schema. Adequate but incomplete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds no meaning beyond the schema for 'sessionId', which is already described as 'ID of the debug session'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'continue' and resource 'program execution', which distinguishes it from sibling tools like 'step' and 'next'. However, it could be more specific, e.g., 'after a breakpoint is hit'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'step', 'next', or 'evaluate'. The agent is left to infer usage context without explicit instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other 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