Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

step_into

Step into function calls during NodeJS debugging to examine internal execution flow and inspect variables within called functions.

Instructions

Steps into function calls

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full handler implementation for the 'step_into' tool. Registers the tool with MCP server and defines the async handler function that ensures the debugger is enabled and paused, then sends the Chrome DevTools Protocol 'Debugger.stepInto' command to step into function calls.
    server.tool(
      "step_into",
      "Steps into function calls",
      {},
      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.stepInto', {});
          
          return {
            content: [{
              type: "text",
              text: "Stepped into function call"
            }]
          };
        } catch (err) {
          return {
            content: [{
              type: "text",
              text: `Error stepping into: ${err.message}`
            }]
          };
        }
      }
    );
  • The server.tool call that registers the 'step_into' tool with the MCP server, including description, empty schema, and inline handler.
    server.tool(
      "step_into",
      "Steps into function calls",
      {},
      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.stepInto', {});
          
          return {
            content: [{
              type: "text",
              text: "Stepped into function call"
            }]
          };
        } catch (err) {
          return {
            content: [{
              type: "text",
              text: `Error stepping into: ${err.message}`
            }]
          };
        }
      }
    );
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 of behavioral disclosure. 'Steps into function calls' implies a debugging action that likely changes execution state, but it doesn't specify whether this requires a paused debugger, what happens to execution flow, or if it's reversible. For a debugging tool with zero annotation coverage, this leaves critical behavioral traits unclear.

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 with zero wasted words. It's front-loaded with the core action and target, making it immediately understandable. Every word earns its place by conveying the essential purpose without redundancy.

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 tools (which often require specific execution states) and the lack of annotations or output schema, the description is incomplete. It doesn't explain prerequisites (e.g., needing a paused debugger), what 'stepping into' entails behaviorally, or what the agent should expect after invocation. For a tool in a debugging context with no structured support, this is inadequate.

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, meaning there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate since no parameters exist, and the description doesn't incorrectly imply any.

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 into function calls' clearly indicates the action (stepping) and target (function calls), which is a specific verb+resource combination. However, it doesn't differentiate this tool from its siblings like 'step_over' or 'step_out', leaving ambiguity about when to use each stepping operation. The purpose is understandable but lacks sibling distinction.

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_over' or 'step_out'. There's no mention of context, prerequisites, or exclusions. Without any usage guidelines, the agent must infer when stepping into is appropriate based solely on the tool name and sibling names.

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