Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

continue

Resume NodeJS code execution after pausing at a breakpoint to continue debugging your application.

Instructions

Continues code execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'continue' MCP tool. Checks if debugger is paused, then sends 'Debugger.resume' command to resume execution and returns status message.
      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}`
            }]
          };
        }
      }
    );
  • Registration of the 'continue' tool using server.tool() with name, description, empty schema, and inline handler function.
    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 provided, the description carries the full burden of behavioral disclosure but provides minimal information. 'Continues code execution' suggests a state-changing operation (resuming execution), but doesn't clarify whether this requires a paused state, what happens to breakpoints, whether it's reversible, or what the expected outcome is. For a debugging tool with zero annotation coverage, this is insufficient.

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 maximally concise with just three words that directly state the tool's action. There's zero wasted language or unnecessary elaboration. Given the tool's simple purpose, this level of brevity is appropriate and efficient.

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 debugging tool with no annotations, no output schema, and multiple sibling tools offering similar step/continue functionality, the description is inadequate. It doesn't explain what differentiates 'continue' from step operations, what state the debugger must be in to use it, or what happens after execution resumes. The context demands more complete guidance.

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?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. While it doesn't add any parameter-specific information beyond what the schema provides, the baseline for zero parameters with complete schema coverage is appropriately a 4.

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

Purpose2/5

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

The description 'Continues code execution' is a tautology that essentially restates the tool name 'continue' without providing meaningful specificity. While it indicates the action (continues) and target (code execution), it doesn't distinguish this tool from potential alternatives or explain what 'continues' means in this debugging context compared to step 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 the many sibling debugging tools (step_into, step_over, step_out, evaluate, etc.). The description doesn't indicate whether this resumes normal execution after hitting a breakpoint, continues from a paused state, or has any specific prerequisites or timing considerations.

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