Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

step_out

Resume execution until the current function returns, allowing you to skip remaining code within the function and continue debugging from the caller.

Instructions

Steps out of current function

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'step_out' tool via server.tool() with name, description, empty schema, and handler callback
    // Step out tool
    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}`
            }]
          };
        }
      }
    );
  • Handler function for step_out: checks debugger is enabled, verifies debugger is paused, sends Debugger.stepOut command via inspector, and returns 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.stepOut', {});
        
        return {
          content: [{
            type: "text",
            text: "Stepped out of current function"
          }]
        };
      } catch (err) {
        return {
          content: [{
            type: "text",
            text: `Error stepping out: ${err.message}`
          }]
        };
      }
    }
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states the action without detailing effects (e.g., call stack changes, side effects, or whether it pauses execution).

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 short sentence that conveys the core action. It could benefit from slight elaboration without being verbose, but it is not overlong.

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 a straightforward action, the description is mostly complete. However, it lacks explanation of the stepping context (e.g., debugger state) and how it differs from similar tools.

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?

Input schema has zero parameters with 100% coverage. Description adds nothing beyond schema, but since no parameters exist, it is sufficient. The schema already indicates no arguments needed.

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 'Steps out of current function' clearly states the tool's action and resource (function). It distinguishes from siblings like 'step_into' and 'step_over' by the direction of stepping, but lacks any additional context.

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 guidelines on when to use this tool vs alternatives (e.g., step_into, step_over). The description does not mention prerequisites or 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