Skip to main content
Glama

Sap Breakpoint List

sap_breakpoint_list
Read-onlyIdempotent

List external ABAP breakpoints for the current user by program, class method, or function module; use this before debugging to review active breakpoints. Desktop backend only.

Instructions

List all external ABAP breakpoints for the current user on a program, class method, or function module. Desktop backend only.

Opens 'Hilfsmittel > Breakpoints > Anzeigen...' dialog in the source editor, reads the grid, and returns matching breakpoints.

Note: if this session is currently stopped at a breakpoint, this tool fails with an error naming the ABAP debugger instead of opening the dialog — continue or exit the debugger in SAP GUI first.

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoSession ID (e.g., "s1"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
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.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
breakpointsNoAll external breakpoints found on the object
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: it discloses that it drives the SAP GUI dialog ('Hilfsmittel > Breakpoints > Anzeigen...') and reads the grid, which is a UI side effect an agent would not infer from the annotations. It also names the exact failure mode and the debugger-state cause, which is precisely the kind of context an agent needs before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope statement is front-loaded, and the usage note appears as a clearly separated caveat. The middle sentence describing the dialog interaction is slightly mechanical but earns its place by setting up the failure-mode note; overall there is little waste.

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?

An output schema exists, so return-value detail is not required, and the description covers the backend limitation, the object-type targets, and the debugger-stopped failure path. Only the session/agent_id binding semantics are left entirely to the schema, which is a minor gap for a 5-parameter tool.

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%, including the PROG/CLAS/FUGR enum and the note that method_name is required for CLAS and FUGR. The description's mention of "program, class method, or function module" reinforces this but adds no syntax, format, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ("List all external ABAP breakpoints") plus the scoping unit ("for the current user") and the target object forms (program, class method, function module). This is clearly distinguishable from the set/delete breakpoint siblings by resource and action, though no alternative is named explicitly.

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 states a hard environmental constraint ("Desktop backend only") and a concrete precondition under which the call will fail (session stopped at a breakpoint — continue or exit first). What is missing is guidance on when to use this versus the related set/delete breakpoint tools, but the context provided is clear and actionable.

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