Skip to main content
Glama
Freight-Art

abapsmith

by Freight-Art
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

abap_debug

Destructive

Set ABAP breakpoints, run programs, step through execution, and inspect stack frames to identify issues.

Instructions

ABAP debugger driver: arm breakpoints, run a program, step, inspect the stack. One session at a time; variables read-only, frames observe-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runNoThe program to trigger (action="start").
stepNocontinue may end the session (status="dead" plus captured output). runToLine/jumpToLine need toLine; jumpToLine also needs server ABAP_ALLOW_DEBUG_JUMP_TO_LINE=true and confirm:"jumpToLine".
forceNostop only — force-terminates a debuggee left attached by an unclean exit (the "Debuggee already attached" error's escape hatch).
frameNo1-based stackPosition from the last STACK section. Read-only.
actionYesstart needs breakpoints+run. step needs stateId+step. stack needs stateId. frame needs stateId+frame. keepalive/stop/status need nothing.
toLineNoRequired for step="runToLine"/"jumpToLine". 1-based line in the current frame's source.
confirmNoRequired for step="jumpToLine": echo "jumpToLine". Ignored otherwise.
stateIdNoFrom the most recent start/step/stack/frame response; a stale id is refused.
breakpointsNo≥1 entry, required for action="start"; kinds may mix and are validated against SAP before arming. Both kinds take optional condition (ABAP expression, suspend only when true) and skipCount (sent to SAP, NOT enforced — use step:"continue").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.2
    • changedInput schema / properties / breakpoints / description
      Previous value: -"≥1 entry, required only for action=\"start\". Line/exception kinds may mix; validated against SAP before arming."New value: +"≥1 entry, required for action=\"start\"; kinds may mix and are validated against SAP before arming. Both kinds take optional condition (ABAP expression, suspend only when true) and skipCount (sent to SAP, NOT enforced — use step:\"continue\")."
    • changedInput schema / properties / breakpoints / items / oneOf
      Previous value: -[
-  {
-    "properties": {
-      "condition": {
-        "description": "ABAP condition expression — breakpoint suspends only when true, e.g. \"sy-tabix = 500\".",
-        "maxLength": 255,
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "line",
-        "type": "string"
-      },
-      "line": {
-        "description": "1-based source line to break at. SAP may snap this to the nearest executable statement — if it does, the start response reports the corrected line.",
-        "maximum": 999999,
-        "minimum": 1,
-        "type": "integer"
-      },
-      "object": {
-        "description": "The class or report to break in (any form abap_read/abap_run accept: bare name, \"class ZCL_FOO\", a raw ADT URI, ...). Resolved server-side to a source URI.",
-        "type": "string"
-      },
-      "skipCount": {
-        "description": "Hits to ignore before suspending (0 = every hit). NOT ENFORCED by this backend — every hit still suspends; use step:\"continue\" instead.",
-        "maximum": 1000000,
-        "minimum": 0,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "kind",
-      "object",
-      "line"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "condition": {
-        "description": "ABAP condition expression — breakpoint suspends only when true, e.g. \"sy-tabix = 500\".",
-        "maxLength": 255,
-        "minLength": 1,
-        "type": "string"
-      },
-      "exceptionClass": {
-        "description": "ABAP exception class to break on when it is raised anywhere, e.g. CX_SY_ZERODIVIDE.",
-        "type": "string"
-      },
-      "kind": {
-        "const": "exception",
-        "type": "string"
-      },
-      "skipCount": {
-        "description": "Hits to ignore before suspending (0 = every hit). NOT ENFORCED by this backend — every hit still suspends; use step:\"continue\" instead.",
-        "maximum": 1000000,
-        "minimum": 0,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "kind",
-      "exceptionClass"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "condition": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "kind": {
+        "const": "line",
+        "type": "string"
+      },
+      "line": {
+        "description": "1-based; SAP may snap it to the nearest executable statement (the start response reports the correction).",
+        "maximum": 999999,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "object": {
+        "description": "Class or report to break in — any form abap_read/abap_run accept.",
+        "type": "string"
+      },
+      "skipCount": {
+        "maximum": 1000000,
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "kind",
+      "object",
+      "line"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "condition": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      },
+      "exceptionClass": {
+        "description": "Exception class to break on, e.g. CX_SY_ZERODIVIDE.",
+        "type": "string"
+      },
+      "kind": {
+        "const": "exception",
+        "type": "string"
+      },
+      "skipCount": {
+        "maximum": 1000000,
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "kind",
+      "exceptionClass"
+    ],
+    "type": "object"
+  }
+]
  2. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: 'One session at a time' reveals a stateful singleton constraint, and 'variables read-only, frames observe-only' clarifies what the driver can and cannot mutate. It does not contradict the readOnlyHint=false or destructiveHint=true annotations because stepping and stopping a debuggee are active operations even though user-visible variables are read-only.

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 two sentences with no filler. The primary verb set is front-loaded, and the second sentence packages three critical constraints compactly. Every clause earns its place.

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?

This is a complex nine-parameter tool with nested breakpoint objects and no output schema, yet the rich input-schema descriptions cover action requirements, return-referenced fields like stateId and status, and edge cases like force and jumpToLine. The description supplies the high-level orientation and the singleton/read-only constraints, which combined with the schema is sufficient for correct invocation.

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 the schema already documents all parameters in detail, including action dependencies, defaults, required fields, and constraints like 'stale id is refused.' The description itself adds little parameter-level meaning beyond orienting the agent to the debugger domain, which matches the baseline-3 case.

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 clearly states the tool is an 'ABAP debugger driver' and lists concrete verbs: 'arm breakpoints, run a program, step, inspect the stack.' This makes the core purpose obvious. However, it does not explicitly distinguish itself from sibling tools like abap_debug_vars or abap_debug_value, though 'variables read-only, frames observe-only' hints at the boundary.

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

Usage Guidelines3/5

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

The description provides useful context: 'One session at a time' warns against concurrent sessions, and 'variables read-only, frames observe-only' signals limitations. But it does not name alternative tools or state explicit when-to-use/when-not-to-use conditions, leaving the agent to infer the routing decision.

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/Freight-Art/abapsmith'

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