Skip to main content
Glama
Sign In
abap-config-mcp

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set ABAP Breakpoint

abap_debug_set_breakpoint

Sets an external SAP breakpoint on a specified source line for a user before a listen session, enabling the program run to pause at that line.

Instructions

Set an external breakpoint on one source line for a user. Returns the breakpoint id (or an error entry), which abap_debug_delete_breakpoint takes. Set breakpoints before abap_debug_session with action listen, then run the program as that user to trigger it. Registers the breakpoint in SAP for that user; it does not change the object's source.

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": {
      "sourceUrl": "<sourceUrl>",
      "line": "<line>"
    },
    "name": "abap_debug_set_breakpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYes1-based line number in that source; use get_abap_object_lines or search_abap_object_lines to find it
usernameNoSAP username (defaults to connected user)
sourceUrlYesADT source URL including /source/main (e.g. /sap/bc/adt/programs/programs/ZREPORT/source/main, /sap/bc/adt/oo/classes/zcl_order_api/source/main)
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.2
    • changedInput schema / properties / line / description
      Previous value: -"Line number for the breakpoint"New value: +"1-based line number in that source; use get_abap_object_lines or search_abap_object_lines to find it"
    • changedInput schema / properties / sourceUrl / description
      Previous value: -"ADT source URL of the object (e.g. /sap/bc/adt/programs/programs/Z_MY_PROG/source/main)"New value: +"ADT source URL including /source/main (e.g. /sap/bc/adt/programs/programs/ZREPORT/source/main, /sap/bc/adt/oo/classes/zcl_order_api/source/main)"
  2. First observedv1.16.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds real context beyond them: the breakpoint is registered in SAP for that user, the object's source is not modified (clarifying the non-destructive hint), and the result is a breakpoint id or an error entry. It does not address re-setting a breakpoint on the same line, which is why idempotentHint=false matters.

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?

Three tight sentences, front-loaded with the action and return value, followed by the sequencing prerequisite and a scope caveat. Every sentence carries information, though the 'does not change source' clause borders on redundant with destructiveHint=false.

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?

With no output schema, the description still explains the return (breakpoint id or error entry) and how to consume it, plus the prerequisite ordering and the non-mutating guarantee. Nothing an agent needs to invoke this correctly 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 all four parameters including sourceUrl examples and the line-lookup helpers are already documented. The description only reinforces per-user scoping and single-line semantics, adding little beyond the schema.

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 ('Set an external breakpoint on one source line for a user') with scope qualifiers (external, single line, per-user) that separate it from abap_debug_delete_breakpoint and abap_debug_session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit ordering: set breakpoints before abap_debug_session with action listen, then run the program as that user to trigger. It also names the consuming sibling (abap_debug_delete_breakpoint takes the returned id), so the workflow position is unambiguous.

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

Deploy Server

Other Tools