Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

delete_debugger_breakpoint

Delete a breakpoint from the SAP debugger using its breakpoint ID. Supports specifying system ID for multi-system environments.

Instructions

Remove a breakpoint from the debugger

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
breakpoint_idYesBreakpoint ID to delete
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Tool registration and input schema for delete_debugger_breakpoint
    name: "delete_debugger_breakpoint",
    description: "Remove a breakpoint from the debugger",
    inputSchema: {
      type: "object" as const,
      properties: {
        breakpoint_id: { type: "string", description: "Breakpoint ID to delete" },
        ...SYSTEM_ID_PROP,
      },
      required: ["breakpoint_id"],
    },
  • Handler that calls client.debuggerDeleteBreakpoint to delete a debugger breakpoint
    case "delete_debugger_breakpoint": {
      const { breakpoint_id } = DebuggerBreakpointIdSchema.parse(args);
      const result = await client.debuggerDeleteBreakpoint(breakpoint_id);
      return { content: [{ type: "text", text: result }] };
    }
  • Actual implementation of debuggerDeleteBreakpoint - sends HTTP DELETE to /sap/bc/adt/debugger/breakpoints/{id}
    async debuggerDeleteBreakpoint(breakpointId: string): Promise<string> {
      this.ensureDebugSession();
      const resp = await this.http.delete(
        `/sap/bc/adt/debugger/breakpoints/${encodeURIComponent(breakpointId)}`,
        { headers: this.statefulHeaders(), responseType: "text" }
      );
      return resp.data as string || "Breakpoint deleted";
    }
  • DebuggerBreakpointIdSchema - validates breakpoint_id input parameter
    const DebuggerBreakpointIdSchema = z.object({ breakpoint_id: z.string() });
  • Debugger section listing all debugger tool definitions including delete_debugger_breakpoint
    },
    // --- Debugger ---
    {
      name: "start_debugger_listener",
      description: "Start an ABAP debugger listener. Opens a stateful session and waits for a debug event. Must call stop_debugger_listener when done.",
      inputSchema: {
        type: "object" as const,
        properties: {
          terminal_id: { type: "string", description: "Terminal identifier (default: MCP_TERMINAL)" },
          ide_id: { type: "string", description: "IDE identifier (default: MCP_IDE)" },
          user: { type: "string", description: "SAP username to debug (default: current user)" },
          ...SYSTEM_ID_PROP,
        },
        required: [],
      },
    },
    {
      name: "stop_debugger_listener",
      description: "Stop the debugger listener and close the stateful debug session",
      inputSchema: {
        type: "object" as const,
        properties: {
          terminal_id: { type: "string", description: "Terminal identifier (default: MCP_TERMINAL)" },
          ide_id: { type: "string", description: "IDE identifier (default: MCP_IDE)" },
          user: { type: "string", description: "SAP username (default: current user)" },
          ...SYSTEM_ID_PROP,
        },
        required: [],
      },
    },
    {
      name: "set_debugger_breakpoint",
      description: "Set a breakpoint at a specific source location in the debugger",
      inputSchema: {
        type: "object" as const,
        properties: {
          uri: { type: "string", description: "Object source URI (e.g. /sap/bc/adt/programs/programs/ztest/source/main)" },
          line: { type: "number", description: "Line number for breakpoint" },
          user: { type: "string", description: "SAP username (default: current user)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["uri", "line"],
      },
    },
    {
      name: "delete_debugger_breakpoint",
      description: "Remove a breakpoint from the debugger",
      inputSchema: {
        type: "object" as const,
        properties: {
          breakpoint_id: { type: "string", description: "Breakpoint ID to delete" },
          ...SYSTEM_ID_PROP,
        },
        required: ["breakpoint_id"],
      },
    },
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention side effects (e.g., is it destructive?), authorization needs, or behavior if the breakpoint does not exist. The description is too minimal for a deletion tool.

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, well-structured sentence with no wasted words. It is front-loaded with the verb 'Remove', making it immediately understandable.

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

Completeness3/5

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

For a simple delete operation with two parameters and no output schema, the description is adequate but not exhaustive. It lacks behavioral context and doesn't mention the optional system_id parameter, but the schema compensates partially.

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% (both parameters described in schema). The description adds no parameter information beyond what the schema already provides, so baseline 3 is appropriate.

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 verb 'Remove' and the resource 'breakpoint' in the context of the debugger. It clearly distinguishes from sibling tools like set_debugger_breakpoint (add) and other debugger 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, no prerequisites (e.g., active debug session), and no exclusions. Sibling tools like set_debugger_breakpoint exist, but no comparison 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/ethanhan2014/sap-adt-mcp'

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