Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

step_over

Advance code execution to the next line, executing the current line without entering function calls to isolate and assess program flow.

Instructions

Steps over to the next line of code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'step_over' tool via server.tool() with name 'step_over' and description 'Steps over to the next line of code'.
    // Step over tool
    server.tool(
      "step_over",
      "Steps over to the next line of code",
      {},
      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.stepOver', {});
          
          return {
            content: [{
              type: "text",
              text: "Stepped over to next line"
            }]
          };
        } catch (err) {
          return {
            content: [{
              type: "text",
              text: `Error stepping over: ${err.message}`
            }]
          };
        }
      }
    );
  • Handler function for the 'step_over' tool. Checks if debugger is enabled and paused, then sends 'Debugger.stepOver' command via the inspector WebSocket.
    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.stepOver', {});
        
        return {
          content: [{
            type: "text",
            text: "Stepped over to next line"
          }]
        };
      } catch (err) {
        return {
          content: [{
            type: "text",
            text: `Error stepping over: ${err.message}`
          }]
        };
      }
    }
  • The Inspector.send() method used by the handler to send the 'Debugger.stepOver' command via WebSocket to the Node.js debugger.
    async send(method, params) {
    	return new Promise((resolve, reject) => {
    		const timeout = setTimeout(() => {
    			reject(new Error(`Request timed out: ${method}`));
    			this.pendingRequests.delete(id);
    		}, 5000);
    		
    		const checkConnection = () => {
    			if (this.connected) {
    				try {
    					const id = Math.floor(Math.random() * 1000000);
    					this.pendingRequests.set(id, { 
    						resolve: (result) => {
    							clearTimeout(timeout);
    							resolve(result);
    						}, 
    						reject: (err) => {
    							clearTimeout(timeout);
    							reject(err);
    						} 
    					});
    					
    					this.ws.send(JSON.stringify({
    						id,
    						method,
    						params
    					}));
    				} catch (err) {
    					clearTimeout(timeout);
    					reject(err);
    				}
    			} else {
    				const connectionCheckTimer = setTimeout(checkConnection, 100);
    				// If still not connected after 3 seconds, reject the promise
    				setTimeout(() => {
    					clearTimeout(connectionCheckTimer);
    					clearTimeout(timeout);
    					reject(new Error('Not connected to debugger'));
    				}, 3000);
    			}
    		};
    		
    		checkConnection();
    	});
    }
  • The schema for 'step_over' - an empty object {} as it takes no parameters.
    {},
Behavior2/5

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

The description is minimal and does not disclose behavioral traits beyond the basic action. No annotations are provided, so the description carries the full burden but fails to mention specifics like whether it executes the current line or if it differs from continue.

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?

One short sentence is appropriately concise. There is no wasted text, and the structure is front-loaded with the core action.

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?

Given no parameters, no output schema, and the presence of sibling debugger tools, the description is somewhat complete. However, it could mention that stepping over does not enter functions, which would provide valuable context for an AI agent deciding between step_over and step_into.

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 no parameters, and the schema coverage is 100%. With zero parameters, the baseline is 4. The description adds minimal value but is acceptable given no params.

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 'Steps over to the next line of code' clearly states the verb (steps over) and the resource (next line of code). It distinguishes from sibling tools like step_into (steps into function calls) and step_out (steps out of current function).

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention contexts where stepping over is appropriate versus stepping into or continuing.

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