abap-config-mcp

Delete ABAP Breakpoint

abap_debug_delete_breakpoint

Idempotent

Removes an external ABAP breakpoint by its ID so the program no longer stops there. Deletes only the SAP breakpoint registration, leaving source code and running debug sessions untouched.

Instructions

Remove one external breakpoint by the id abap_debug_set_breakpoint returned. Use it when a breakpoint should no longer stop the program; it does not end a running debug session (use abap_debug_session with detach, or abap_debug_step with terminateDebuggee, for that). Removes the breakpoint registration in SAP only; source is untouched.

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": {
      "breakpointId": "<breakpointId>"
    },
    "name": "abap_debug_delete_breakpoint"
  }
}

Input Schema

Name	Required	Description
`username`	No	SAP username (defaults to connected user)
`breakpointId`	Yes	Breakpoint id returned by abap_debug_set_breakpoint
`connectionId`	No	SAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.16.0Nov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: the effect is limited to the SAP breakpoint registration, source is untouched, and a running debug session is not ended. It does not state what happens when the breakpointId is unknown or already deleted (error vs. silent success), which is the main residual gap.

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?

Three short sentences, front-loaded with the action and scope, then the negative guidance with named alternatives, then the blast radius. No filler and nothing repeated.

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?

For a three-parameter mutation with no output schema, the definition covers scope, exclusions, alternatives, and side-effect boundaries, and annotations carry the safety hints. Only the behavior on an invalid or already-removed id is left unspecified.

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 three parameters are documented, including that breakpointId comes from abap_debug_set_breakpoint. The description restates that provenance but adds no format, validation, or defaulting 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Remove one external breakpoint') and ties the input to its producer ('by the id abap_debug_set_breakpoint returned'). This makes it immediately distinguishable from abap_debug_set_breakpoint and from the session/step tools.

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 an explicit when ('when a breakpoint should no longer stop the program') and an explicit when-not, naming two concrete alternatives: abap_debug_session with detach and abap_debug_step with terminateDebuggee. An agent needs no inference to route between these tools.

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

Deploy Server