Skip to main content
Glama

continue

Resume execution of a paused Go debug session to continue program flow and identify subsequent issues.

Instructions

Continue program execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the debug session

Implementation Reference

  • Executes the 'continue' tool by sending a Delve 'Command' with name 'continue' to the specified session and returns a text confirmation.
    case "continue": {
      await sendDelveCommand(session, "Command", { name: "continue" });
      return {
        content: [{
          type: "text",
          text: "Continued execution"
        }]
      };
    }
  • Defines the input schema for the 'continue' tool, requiring a 'sessionId' string.
    inputSchema: {
      type: "object",
      properties: {
        sessionId: {
          type: "string",
          description: "ID of the debug session"
        }
      },
      required: ["sessionId"]
    }
  • src/server.ts:181-194 (registration)
    Registers the 'continue' tool in the ListTools response, including name, description, and input schema.
    {
      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)
    Dispatches calls to the 'continue' tool (and other control tools) to the handleControlCommands function in the central CallToolRequest handler.
    if (["setBreakpoint", "removeBreakpoint", "continue", "next", "step", "stepout", "variables", "evaluate"].includes(name)) {
      return handleControlCommands(name, args);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose what 'continue' means operationally (e.g., resumes execution until next breakpoint or program end), whether it's safe/reversible, or any side effects. The agent must infer behavior from the tool name alone.

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

Conciseness5/5

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

The description is extremely concise with just three words, front-loaded with the verb 'Continue'. There is zero wasted text, though this conciseness comes at the cost of completeness.

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

Completeness2/5

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

For a debug control tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'continue' does in debugging context, what happens after execution resumes, or how it differs from similar sibling tools. The agent lacks sufficient context to use this tool effectively.

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 description coverage is 100% for the single parameter 'sessionId', so the schema fully documents it. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline for high schema coverage.

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

Purpose3/5

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

The description 'Continue program execution' states a clear action (continue) but is vague about what specifically is being continued. It doesn't specify this is for debugging sessions or distinguish it from sibling tools like 'next', 'step', or 'stepout' which are also debug control operations.

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 is provided about when to use this tool versus alternatives like 'next', 'step', or 'stepout'. The description doesn't mention prerequisites (e.g., requires an active debug session) or context for when continuation is appropriate versus stepping through code.

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