Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

continue

Advance code execution from a paused state to the next breakpoint or program completion, enabling step-by-step debugging.

Instructions

Continues code execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'continue' tool via server.tool() with a handler that resumes debugger execution
    server.tool(
      "continue",
      "Continues code execution",
      {},
      async () => {
        try {
          // Ensure debugger is enabled
          if (!inspector.debuggerEnabled) {
            await inspector.enableDebugger();
          }
          
          if (!inspector.paused) {
            return {
              content: [{
                type: "text",
                text: "Debugger is not paused at a breakpoint"
              }]
            };
          }
          
          await inspector.send('Debugger.resume', {});
          
          return {
            content: [{
              type: "text",
              text: "Execution resumed"
            }]
          };
        } catch (err) {
          return {
            content: [{
              type: "text",
              text: `Error continuing execution: ${err.message}`
            }]
          };
        }
      }
    );
Behavior2/5

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

With no annotations, the description must disclose behaviors. 'Continues code execution' does not explain what happens (e.g., runs until next breakpoint, program end, or forever). Side effects are unclear.

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

Conciseness2/5

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

While it is short, it is under-specified. Every sentence does not earn its place because the single sentence fails to provide enough value for an AI agent.

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?

Given the zero-parameter input and no output schema, the description is still incomplete. It does not explain the tool's role in debugging or what 'continue' means in context.

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

Parameters4/5

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

No parameters exist, so schema coverage is 100%. The description adds no parameter info, but none is needed. Baseline 4 is appropriate.

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 verb 'continues' and resource 'code execution' clearly indicate the tool's action. It is distinct from step_into/step_over which imply incremental stepping, but could be more explicit that it resumes full execution.

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 siblings like step_over or step_into. The description lacks context about typical debugging scenarios.

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/workbackai/mcp-nodejs-debugger'

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