Skip to main content
Glama

setBreakpoint

Set a breakpoint in Go programs during debugging sessions to pause execution at specific lines and inspect code behavior.

Instructions

Set a breakpoint in the debugged program

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the debug session
fileYesFile path where to set the breakpoint
lineYesLine number for the breakpoint
conditionNoOptional condition for the breakpoint

Implementation Reference

  • Executes the setBreakpoint tool: destructures args for file, line, condition; sends CreateBreakpoint command to Delve session; creates and stores Breakpoint object; returns success message.
    case "setBreakpoint": {
      const { file, line, condition } = args;
      const response = await sendDelveCommand(session, "CreateBreakpoint", {
        file,
        line,
        cond: condition
      });
    
      const bp: Breakpoint = {
        id: response.id,
        file,
        line,
        condition
      };
      session.breakpoints.set(bp.id, bp);
    
      return {
        content: [{
          type: "text",
          text: `Set breakpoint ${bp.id} at ${file}:${line}`
        }]
      };
    }
  • Defines the input schema and metadata for the setBreakpoint tool, specifying required parameters sessionId, file, line and optional condition.
      name: "setBreakpoint",
      description: "Set a breakpoint in the debugged program",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: {
            type: "string",
            description: "ID of the debug session"
          },
          file: {
            type: "string",
            description: "File path where to set the breakpoint"
          },
          line: {
            type: "number",
            description: "Line number for the breakpoint"
          },
          condition: {
            type: "string",
            description: "Optional condition for the breakpoint"
          }
        },
        required: ["sessionId", "file", "line"]
      }
    },
  • src/server.ts:411-413 (registration)
    Routes calls to the setBreakpoint tool (and other control tools) to the handleControlCommands function within the CallToolRequestSchema handler.
    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 full burden for behavioral disclosure. While 'Set a breakpoint' implies a mutation operation, it doesn't specify whether this requires specific permissions, what happens if the breakpoint already exists, or any side effects. No rate limits, error conditions, or response format are mentioned.

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 appropriately sized for a tool with good schema documentation and gets straight to the point.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after setting the breakpoint, what the response contains, or any behavioral nuances. Given the complexity of debugging operations, more context is needed.

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 description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high coverage.

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 clearly states the action ('Set a breakpoint') and target ('in the debugged program'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'removeBreakpoint' or explain how it differs from other debugging operations.

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 'removeBreakpoint' or other debugging commands. There's no mention of prerequisites (e.g., needing an active debug session) or contextual constraints.

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