mcp-abap-adt

DeleteLocalDefinitions

Delete local definitions from an ABAP class by clearing its definitions include, handling lock, update, unlock, and optional activation automatically.

Instructions

Delete local definitions from an ABAP class by clearing the definitions include. Manages lock, update, unlock, and optional activation. 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": {
      "class_name": "<class_name>"
    },
    "name": "DeleteLocalDefinitions"
  }
}

Input Schema

Name	Required	Description	Default
`detail`	No	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).	terse
`class_name`	Yes	Parent class name.
`transport_request`	No	Transport request number, not a task.
`activate_on_delete`	No	Activate parent class after deleting. Default: false

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv16.0.0Oct 4, 2026

changedInput schema / properties / class_name / description

Previous value: -"Parent class name (e.g., ZCL_MY_CLASS)."New value: +"Parent class 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."New value: +"Transport request number, not a task."

First observedDec 29, 2025

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses lock/update/unlock lifecycle handling, optional activation, and batch-mode exclusion, but omits permissions, reversibility, and error behavior for a destructive operation.

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 purpose and mechanism, followed by operational constraints. No filler or redundancy.

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 mutation with no annotations and no output schema, it gives the operational flow but lacks prerequisites, permission requirements, and expected results. An agent can call it, but cannot fully predict side effects or confirmation behavior.

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 baseline is 3. The description only echoes optional activation; class_name, transport_request, and detail are left to the schema descriptions.

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: 'Delete local definitions from an ABAP class,' and clarifies the mechanism as clearing the definitions include. This clearly distinguishes it from sibling tools like GetLocalDefinitions, UpdateLocalDefinitions, DeleteLocalTypes, and DeleteLocalMacros.

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

Usage Guidelines2/5

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

Provides no explicit when-to-use or when-not guidance and does not name alternatives. The only usage-related constraint is 'Runs outside batch mode,' which is operational rather than selection guidance.

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

Deploy Server