Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

step_out

Step out of the current function during NodeJS debugging to resume execution at the caller's level.

Instructions

Steps out of current function

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that checks if debugger is paused, then sends 'Debugger.stepOut' command to the inspector, returning success or error 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.stepOut', {});
        
        return {
          content: [{
            type: "text",
            text: "Stepped out of current function"
          }]
        };
      } catch (err) {
        return {
          content: [{
            type: "text",
            text: `Error stepping out: ${err.message}`
          }]
        };
      }
    }
  • Registration of the 'step_out' tool with server.tool, including name, description, empty schema, and handler function.
    server.tool(
      "step_out",
      "Steps out of current function",
      {},
      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.stepOut', {});
          
          return {
            content: [{
              type: "text",
              text: "Stepped out of current function"
            }]
          };
        } catch (err) {
          return {
            content: [{
              type: "text",
              text: `Error stepping out: ${err.message}`
            }]
          };
        }
      }
    );
  • Empty input schema (no parameters required).
    {},
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action but doesn't disclose behavioral traits such as whether this is a read-only operation, if it affects program state, what happens after stepping out (e.g., pauses execution), or any side effects. This is a significant gap for a tool that likely involves execution control.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words, making it easy to parse. However, it could be more front-loaded with additional context (e.g., 'In a debugging session, steps out of the current function') to improve clarity without sacrificing brevity.

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 a step-out operation in debugging (likely involving execution control), the description is incomplete. No annotations or output schema exist to provide behavioral or return value details, and the description lacks context on prerequisites, effects, or what to expect after use, making it inadequate for safe and effective tool invocation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, but it also doesn't compensate for any gaps since there are none. Baseline is 4 for 0 parameters, as the schema fully covers the absence of inputs.

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

Purpose3/5

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

The description 'Steps out of current function' clearly indicates the action (step out) and target (current function), but it's vague about the context—it doesn't specify if this is for debugging, execution control, or a specific environment. It distinguishes from siblings like 'step_into' and 'step_over' by implying a different direction, but lacks explicit differentiation.

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 on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., being in a debugging session), exclusions, or comparisons to siblings like 'step_into' or 'step_over', leaving the agent to infer usage from context 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