Skip to main content
Glama

Sap Breakpoint Delete

sap_breakpoint_delete

Delete an external ABAP breakpoint from a program, class method, or function module by line number or source match pattern; reports when the breakpoint was not set.

Instructions

Delete an external ABAP breakpoint on a specific line of a program, class method, or function module. Desktop backend only.

Provide either line_number (1-indexed SAP display line) or match_pattern (substring or regex matched against source lines).

If the line has no breakpoint, SAP sets one. This tool detects that and re-applies to undo it, then reports action='was_not_set'.

Note: this only removes the breakpoint from the source editor. It does NOT step or continue a debugger that is currently stopped and showing a modal dialog — there is no tool for that; only a human at the SAP GUI can dismiss it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object_type": "<object_type>",
      "object_name": "<object_name>"
    },
    "name": "sap_breakpoint_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoSession ID (e.g., "s1"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
line_numberNo1-indexed SAP display line. Mutually exclusive with match_pattern.
method_nameNoRequired for CLAS (method name) and FUGR (function module name).
object_nameYesProgram name, class name, or function group name.
object_typeYes"PROG" for programs, "CLAS" for classes, "FUGR" for function groups.
match_patternNoSubstring or regex matched against source. Mutually exclusive with line_number.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
actionNoWhat actually happeneddeleted
successNoWhether the operation succeeded
line_numberNo1-indexed line number
method_nameNoMethod or function module name (None for PROG)
object_nameYesProgram name, class name, or function group name
object_typeYesObject type: PROG, CLAS, or FUGR
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
status_messageNoRaw SAP status bar message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Discloses a non-obvious side effect that annotations do not cover: if no breakpoint exists on the line, SAP sets one and the tool re-applies to undo it, reporting action='was_not_set'. It also flags the hard limitation that it cannot dismiss a modal debugger dialog, which prevents a plausible failed call. This is consistent with readOnlyHint=false and idempotentHint=false.

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?

Front-loaded with the verb and resource, then the parameter-selection rule, then the caveats. Every sentence carries operational information; there is no filler or restatement of the title.

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

Completeness5/5

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

Covers the two targeting modes, the CLAS/FUGR method requirement implicitly via scope wording, the backend restriction, the no-breakpoint edge case, and the modal-dialog limitation. With an output schema present, return values need no explanation, so nothing an agent needs before calling is missing.

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 line_number (1-indexed display line), match_pattern (substring or regex), and method_name requirements are already documented in the schema. The description restates the line_number/match_pattern mutual exclusivity but adds no new format or semantic detail beyond that. 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?

States a specific verb and resource ("Delete an external ABAP breakpoint on a specific line of a program, class method, or function module") and names the exact target scope. An agent can distinguish this from sap_breakpoint_set and sap_breakpoint_list purely from the text.

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?

Gives clear selection guidance between the two targeting modes ("Provide either line_number ... or match_pattern") and an explicit environment restriction ("Desktop backend only"). It also states a when-not case (a stopped debugger with a modal dialog cannot be handled by any tool), though it never names sap_breakpoint_set as the counterpart for setting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.