Skip to main content
Glama

next

Step over to the next line during Go debugging sessions to continue code execution and analyze program flow.

Instructions

Step over to next line

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the debug session

Implementation Reference

  • The core handler logic for the 'next' tool: sends a 'next' command to the Delve debug session and returns a success message.
    case "next": {
      await sendDelveCommand(session, "Command", { name: "next" });
      return {
        content: [{
          type: "text",
          text: "Stepped to next line"
        }]
      };
    }
  • Defines the input schema for the 'next' tool, requiring a sessionId.
    {
      name: "next",
      description: "Step over to next line",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: {
            type: "string",
            description: "ID of the debug session"
          }
        },
        required: ["sessionId"]
      }
  • src/server.ts:195-207 (registration)
    Registers the 'next' tool in the tools array provided to the MCP server.
    {
      name: "next",
      description: "Step over to next line",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: {
            type: "string",
            description: "ID of the debug session"
          }
        },
        required: ["sessionId"]
      }
  • src/server.ts:411-413 (registration)
    Routes calls to the 'next' tool to the handleControlCommands function.
    if (["setBreakpoint", "removeBreakpoint", "continue", "next", "step", "stepout", "variables", "evaluate"].includes(name)) {
      return handleControlCommands(name, args);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Step over to next line' suggests a read-only debugging operation but doesn't clarify if it modifies program state, requires specific debug session states, has side effects, or what happens on execution. It lacks details on permissions, rate limits, or error conditions.

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 extremely concise with just three words, 'Step over to next line', which is front-loaded and wastes no space. It efficiently conveys the core action without unnecessary elaboration, making it easy to parse quickly.

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 and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'step over' means operationally, what the tool returns, or how it interacts with other debugging commands. For a tool in a set with many siblings like 'step' and 'stepout', more context is needed to guide proper use.

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 100% description coverage for the single parameter 'sessionId', so the schema fully documents it. The description doesn't add any parameter-specific information, which is acceptable given the high schema coverage. With zero parameters needing extra explanation, this meets the baseline for good coverage.

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 'Step over to next line' indicates a debugging action but is vague about what resource it operates on. It doesn't specify whether this steps over function calls or just moves to the next line of code, and it doesn't distinguish itself from sibling tools like 'step', 'stepout', or 'continue' in the debugging 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 guidance is provided on when to use this tool versus alternatives like 'step', 'stepout', or 'continue'. The description implies a debugging step action but offers no context about prerequisites, when it's appropriate, or what distinguishes it from other stepping commands.

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/dwisiswant0/delve-mcp'

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