mcp-abap-adt

CreateClass

Creates an initial ABAP class object in a specified package so source code can be added later through a class update.

Instructions

Creates the ABAP class named by class_name in the package named by package_name, in initial state: the class object alone; its source code is written by an update of the class. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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>",
      "package_name": "<package_name>"
    },
    "name": "CreateClass"
  }
}

Input Schema

Name	Required	Description	Default
`final`	No	Mark class as final. Default: false
`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
`abstract`	No	Mark class as abstract. Default: false
`class_name`	Yes	Class name.
`superclass`	No	Optional superclass name.
`description`	No	Class description (defaults to class_name).
`package_name`	Yes	Package name.
`master_language`	No	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
`create_protected`	No	Protected constructor. Default: false
`transport_request`	No	Transport request number (required for transportable packages), not a task.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv16.0.0Oct 4, 2026

changedInput schema / properties / class_name / description

Previous value: -"Class name (e.g., ZCL_TEST_CLASS_001)."New value: +"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 / package_name / description

Previous value: -"Package name (e.g., ZOK_LAB, $TMP)."New value: +"Package name."

changedInput schema / properties / transport_request / description

Previous value: -"Transport request number (required for transportable packages)."New value: +"Transport request number (required for transportable packages), not a task."

Changed1 schema field changedv8.1.0Jun 26, 2026

addedInput schema / properties / master_language

Added value: +{
+  "description": "Optional master/original language for the created object (e.g. \"EN\", \"DE\", \"ZH\"). Defaults to the session language (SAP_LANGUAGE) or EN.",
+  "type": "string"
+}

Changed2 schema fields changedMar 14, 2026

removedInput schema / properties / activate

Removed value: -{
-  "description": "Activate after creation. Default: true.",
-  "type": "boolean"
-}

removedInput schema / properties / source_code

Removed value: -{
-  "description": "Full ABAP class source code. If omitted, a minimal template is generated.",
-  "type": "string"
-}

First observedDec 29, 2025

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose two non-obvious traits: the object is created with no source code, and in batch mode the call is merely recorded and returns empty content that must be read back by number. It omits permission, transport, and error/failure behavior, which keeps it below a 5.

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?

Two tight sentences with the core creation semantics front-loaded and the batch-mode caveat appended. No filler or repetition of the title.

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?

Given a 10-parameter mutation tool with no annotations and no output schema, the description covers the key facts an agent needs: what exists after the call and how batch answers are retrieved. It could say more about the transport_request prerequisite for transportable packages and what the detail levels return.

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 every one of the 10 parameters is already documented in the schema. The description reiterates class_name and package_name semantics but adds no extra meaning for the boolean flags, the detail enum, or transport_request (whose 'not a task' caveat lives only in the schema).

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?

States a specific verb (Creates) and resource (ABAP class) and pins the scope to class_name/package_name. The clause 'in initial state: the class object alone; its source code is written by an update of the class' implicitly differentiates it from UpdateClass, though the sibling is never named.

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?

Conveys that this tool only creates the shell and that source population belongs to a separate update step, which is useful routing information. However, no alternative tool is named explicitly and there is no when-not-to-use guidance (e.g. if the class already exists).

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

Deploy Server