Skip to main content
Glama

step_into

Steps into a function call during a paused debugging session to examine internal code execution.

Instructions

Steps into a function call if the current line contains one, otherwise steps to the next statement. Use this to examine what happens inside a function. The session must be paused.

Input Schema

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

Implementation Reference

  • Low-level CDP client method that calls Chrome Debugger Protocol's Debugger.stepInto to step into a function call.
    async stepInto(): Promise<void> {
      this.ensureConnected();
      await this.client!.Debugger.stepInto({});
    }
  • Session manager method that retrieves the session, ensures it is paused, and calls the CDP client's stepInto.
    async stepInto(sessionId: string): Promise<void> {
      const session = this.getSession(sessionId);
      this.ensurePaused(session);
      await session.cdpClient.stepInto();
    }
  • Server handler that parses the session_id input, calls sessionManager.stepInto, and returns a success response with 'stepping' state.
    case 'step_into': {
      const params = z.object({session_id: z.string()}).parse(args);
    
      await sessionManager.stepInto(params.session_id);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                success: true,
                state: 'stepping',
              },
              null,
              2
  • Input schema definition for the step_into tool, requiring a 'session_id' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        session_id: {
          type: 'string',
          description: 'ID of the debugging session. The session must be paused.',
        },
      },
      required: ['session_id'],
    },
  • src/server.ts:209-223 (registration)
    Tool registration entry with name 'step_into', description, and input schema, registered alongside other debugging tools.
      name: 'step_into',
      description:
        'Steps into a function call if the current line contains one, otherwise steps to the next statement. ' +
        'Use this to examine what happens inside a function. 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'],
      },
    },
Behavior3/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 describes the conditional step-in behavior and the pause requirement, but lacks details on failure modes, side effects, or state changes beyond the step operation.

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 with the main action front-loaded. Every word serves a purpose, and there is no unnecessary repetition.

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 one-parameter tool with no output schema, the description covers the core behavior, when to use, and prerequisites. It is mostly complete, though it could mention the effect on execution state.

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?

With 100% schema coverage, the baseline is 3. The description repeats the session pause prerequisite, adding marginal value. No further format or validation details are provided.

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 into a function call if present, otherwise steps to the next statement. This specifies the verb and resource, and the conditional behavior distinguishes it from siblings like step_over or step_out.

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?

It explicitly says 'Use this to examine what happens inside a function' and notes the session must be paused. While it does not state when not to use it, the context is clear and the prerequisite is given.

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