Skip to main content
Glama
AerialByte

mcp-netcoredbg

by AerialByte

continue

:

Instructions

Continue program execution until next breakpoint or program end

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdNoThread ID to continue (defaults to current thread)
sessionIdNoSession ID (defaults to current session). Use list_sessions to see available sessions.

Implementation Reference

  • The main handler function for the 'continue' tool. It retrieves the session and calls session.continue(threadId), returning a text response.
    // Tool: continue
    server.tool(
      "continue",
      "Continue program execution until next breakpoint or program end",
      {
        threadId: z
          .number()
          .optional()
          .describe("Thread ID to continue (defaults to current thread)"),
        sessionId: sessionIdParam,
      },
      async ({ threadId, sessionId }) => {
        const session = sessionManager.getSession(sessionId);
        await session.continue(threadId);
    
        return textResponse(`${sessionPrefix(session.id)}Continuing execution...`);
      }
    );
  • Registration entry point for all execution tools including 'continue'. The registerExecutionTools function registers the tool with the MCP server.
    export function registerExecutionTools(server: McpServer): void {
  • Schema definition for the sessionId parameter used by the continue tool. It's an optional string that defaults to the current session.
    export const sessionIdParam = z
      .string()
      .optional()
      .describe("Session ID (defaults to current session). Use list_sessions to see available sessions.");
  • The DebugSession.continue() method that implements the core logic. It validates the client and forwards the continue request to the DAP client with the appropriate thread ID.
    async continue(threadId?: number): Promise<void> {
      const client = this.requireClient();
      await client.continue(threadId || this.lastStoppedThreadId || 1);
      this.lastStoppedReason = null;
      this.lastStoppedThreadId = null;
    }
  • The low-level DAPClient.continue() method that sends the actual 'continue' request to the netcoredbg debugger via the DAP protocol.
    async continue(threadId?: number): Promise<void> {
      const tid = threadId || this.currentThreadId;
      if (!tid) {
        throw new Error("No thread ID available. Is the debugger stopped?");
      }
      await this.sendRequest("continue", { threadId: tid });
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the core behavioral trait (runs freely until breakpoint or termination) but omits state prerequisites (requires paused program), completion behavior, or error conditions.

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?

Single sentence with zero waste. Every word earns its place: the verb, the resource, and the terminal conditions are all essential information front-loaded efficiently.

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

Completeness4/5

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

Given 100% schema coverage and standard debugger semantics, the description is sufficient for correct invocation. Minor gap: does not explicitly state the prerequisite that the program must be in a paused state to use this tool.

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%, documenting both threadId and sessionId defaults. The description adds no parameter-specific semantics, but the baseline score of 3 is appropriate when the schema fully documents parameters.

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

Purpose5/5

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

The description provides a specific verb ('Continue'), resource ('program execution'), and precise behavioral scope ('until next breakpoint or program end'). It clearly distinguishes from sibling stepping tools (step_into, step_over) which stop at line boundaries rather than running freely.

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

Usage Guidelines3/5

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

The description implies usage through 'until next breakpoint,' suggesting when execution stops, but lacks explicit when-to-use guidance (e.g., 'use when resuming from a paused state') or explicit contrasts with alternatives like step_into or pause.

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/AerialByte/mcp-netcoredbg'

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