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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

DeleteBehaviorDefinition

Deletes an ABAP behavior definition from an SAP system through the ADT deletion API, with an optional transport request for local objects.

Instructions

Delete an ABAP behavior definition from the SAP system via ADT deletion API. Transport request optional for local objects. Runs outside batch mode.

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": {
      "behavior_definition_name": "<behavior_definition_name>"
    },
    "name": "DeleteBehaviorDefinition"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
transport_requestNoTransport request number, not a task. Required for transportable objects. Optional for local objects.
behavior_definition_nameYesBehaviorDefinition name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv16.0.0
    • changedInput schema / properties / behavior_definition_name / description
      Previous value: -"BehaviorDefinition name (e.g., Z_MY_BEHAVIORDEFINITION)."New value: +"BehaviorDefinition name."
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required for transportable objects. Optional for local objects ($TMP)."New value: +"Transport request number, not a task. Required for transportable objects. Optional for local objects."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose two meaningful traits beyond the name: the transport-request requirement varies by object type (local vs. transportable) and the operation cannot be run inside BatchBegin/BatchEnd. It stops short of stating what exactly is destroyed, whether the deletion is recoverable, or what errors occur when the object is locked or in a transport.

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 with the action and scope front-loaded, followed by the two non-obvious constraints. No filler, no repetition of the schema, and every sentence contributes a distinct fact.

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

Completeness3/5

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

For a destructive, non-idempotent operation with no annotations and no output schema, the description covers the essentials to call it but leaves gaps: no indication of what happens on failure, whether an inactive object can be deleted, or whether a transport lock blocks the call. Adequate but not complete for a delete 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%, so the schema already documents all three parameters including the transport_request and detail enums, making 3 the baseline. The description's 'transport request optional for local objects' merely restates the schema's own wording and adds no syntax, format, or example for the optional transport number.

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 plus resource ('Delete an ABAP behavior definition') and identifies the underlying mechanism ('via ADT deletion API'), which clearly separates it from the many Get*/Create*/Update* behavior-definition siblings. It never explicitly contrasts with the closest look-alikes (DeleteBehaviorImplementation, DeleteServiceDefinition), but the resource noun is specific enough that confusion is unlikely.

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?

'Transport request optional for local objects' and 'Runs outside batch mode' give real usage context for how to invoke it. However, there is no explicit when-to-use/when-not guidance, no prerequisite statement (e.g. object must exist or be inactive), and no routing to alternatives such as deactivating rather than deleting.

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