Skip to main content
Glama

step_over

Advance execution to the next line in the current function, running any function call fully without stepping into it, when the debug session is paused.

Instructions

Steps over the current statement to the next line in the same function. If the current line contains a function call, the entire function executes without stepping into it. The session must be paused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesID of the debugging session. The session must be paused.

Implementation Reference

  • src/server.ts:191-207 (registration)
    Tool registration: defines the 'step_over' tool with name, description, and inputSchema (requires session_id).
    {
      name: 'step_over',
      description:
        'Steps over the current statement to the next line in the same function. ' +
        'If the current line contains a function call, the entire function executes without stepping into it. ' +
        'The session must be paused.',
      inputSchema: {
        type: 'object',
        properties: {
          session_id: {
            type: 'string',
            description: 'ID of the debugging session. The session must be paused.',
          },
        },
        required: ['session_id'],
      },
    },
  • Handler: parses session_id from args, calls sessionManager.stepOver(), returns success/stepping state.
    case 'step_over': {
      const params = z.object({session_id: z.string()}).parse(args);
    
      await sessionManager.stepOver(params.session_id);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                success: true,
                state: 'stepping',
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Helper: sessionManager.stepOver() retrieves the session, ensures it is paused, then delegates to cdpClient.stepOver().
    async stepOver(sessionId: string): Promise<void> {
      const session = this.getSession(sessionId);
      this.ensurePaused(session);
      await session.cdpClient.stepOver();
    }
  • Helper: cdpClient.stepOver() calls Chrome DevTools Protocol Debugger.stepOver via the CDP client.
    async stepOver(): Promise<void> {
      this.ensureConnected();
      await this.client!.Debugger.stepOver({});
    }
  • Input schema for step_over: an object with required string session_id.
    inputSchema: {
      type: 'object',
      properties: {
        session_id: {
          type: 'string',
          description: 'ID of the debugging session. The session must be paused.',
        },
      },
      required: ['session_id'],
    },
Behavior4/5

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

No annotations are provided, but the description discloses key behavioral traits: it steps over function calls (executing them without stepping into) and requires a paused session. This gives sufficient transparency for an agent to understand the tool's behavior.

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 two sentences long, front-loads the core action, and avoids unnecessary words. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description covers the essential behavior and context. The sibling tools provide differentiation, and the description is complete enough for an agent to understand when and how to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description for 'session_id' that already includes the prerequisite about the session being paused. The tool description does not add additional parameter meaning beyond what the schema provides, so it meets the baseline but does not exceed it.

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 clearly states the tool steps over the current statement to the next line in the same function, and distinguishes it from stepping into or out of functions. It uses a specific verb ('steps over') and resource ('current statement'), making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use it (when debugging and wanting to skip function calls) and notes the prerequisite that the session must be paused. However, it does not explicitly state when not to use it or mention alternatives among siblings.

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/johngrimes/mcp-js-debugger'

If you have feedback or need assistance with the MCP directory API, please join our Discord server