Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

step_over

Step over the current line of code in NodeJS debugging to execute it and pause at the next line, without entering function calls.

Instructions

Steps over to the next line of code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the step_over tool: ensures debugger is enabled and paused, then sends the CDP Debugger.stepOver command, returning success or error messages.
    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}`
          }]
        };
      }
    }
  • Registers the step_over tool using server.tool() with name, description, empty schema, and inline handler function.
    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}`
            }]
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't explain key behavioral aspects: whether it requires a paused debugger state, what happens if no next line exists, whether it affects variable inspection, or what the visual/state outcome is. For a debugging operation 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 a single, efficient sentence that directly states the tool's action without any wasted words. It's front-loaded with the core functionality and appropriately sized for a simple operation.

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 complexity of debugging operations (interacting with execution state), lack of annotations, and no output schema, the description is incomplete. It doesn't address prerequisites, side effects, error conditions, or what 'next line' means contextually. For a tool in a debugging suite with 12 siblings, more contextual guidance is needed.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it correctly avoids mentioning any parameters. Baseline 4 is appropriate for a zero-parameter tool where the schema handles documentation.

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 description clearly states the action ('steps over') and target ('to the next line of code'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'step_into' or 'step_out', which would require more specific context about debugging flow control.

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 like 'step_into', 'step_out', or 'continue'. It lacks context about debugging scenarios, prerequisites (e.g., being paused at a breakpoint), or exclusions, leaving the agent to infer usage from tool names alone.

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