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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateDataElement

Create a new ABAP data element in SAP systems to define reusable field types, initializing the object outside batch mode.

Instructions

Create a new ABAP data element in SAP system. Creates the data element object in initial state. 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": {
      "data_element_name": "<data_element_name>",
      "package_name": "<package_name>"
    },
    "name": "CreateDataElement"
  }
}

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
lengthNoData type length. Usually inherited from domain.
decimalsNoDecimal places. Usually inherited from domain.
data_typeNoData type (e.g., CHAR, NUMC) or domain name when type_kind is 'domain'.CHAR
type_kindNoType kind: 'domain' (default), 'predefinedAbapType', 'refToPredefinedAbapType', 'refToDictionaryType', 'refToClifType'. If not specified, defaults to 'domain'.domain
type_nameNoType name: domain name (when type_kind is 'domain'), data element name (when type_kind is 'refToDictionaryType'), or class name (when type_kind is 'refToClifType')
long_labelNoLong field label (max 40 chars). Applied during update step after creation.
descriptionNoData element description. If not provided, data_element_name will be used.
search_helpNoSearch help name. Applied during update step after creation.
short_labelNoShort field label (max 10 chars). Applied during update step after creation.
medium_labelNoMedium field label (max 20 chars). Applied during update step after creation.
package_nameYesPackage name
heading_labelNoHeading field label (max 55 chars). Applied during update step after creation.
master_languageNoOptional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
data_element_nameYesData element name.
set_get_parameterNoSet/Get parameter ID. Applied during update step after creation.
transport_requestNoTransport request number, not a task. Required for transportable packages.
search_help_parameterNoSearch help parameter. Applied during update step after creation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv16.0.0
    • changedInput schema / properties / data_element_name / description
      Previous value: -"Data element name (e.g., ZZ_E_TEST_001). Must follow SAP naming conventions."New value: +"Data element 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_LOCAL, $TMP for local objects)"New value: +"Package name"
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required for transportable packages."New value: +"Transport request number, not a task. Required for transportable packages."
  2. Changed1 schema field changedv8.1.0
    • 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"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two important behaviors: the object is left in an initial (not usable/activated) state, and the tool cannot run in batch mode. It does not cover failure modes on name collision, permission requirements, or the fact that label/search-help parameters are applied in a second update step.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the core action front-loaded and the two behavioral caveats following. Minimal waste, though "Creates the data element object" slightly restates the opening clause.

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 an 18-parameter creation tool with no annotations and no output schema, the description covers the essentials (initial state, non-batch) but leaves out what the agent most needs next: that activation via ActivateDataElement is required, and whether transport_request is mandatory for transportable packages.

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 18 parameters are already documented in the schema, including the post-creation update-step note on label fields and the transport request caveat. The description adds nothing beyond that, so baseline 3 applies.

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 states a specific verb and resource ("Create a new ABAP data element") and a meaningful scope detail ("in initial state"). Siblings like UpdateDataElement, CheckDataElement, and ActivateDataElement are distinguishable by name, but the description does not explicitly contrast with them.

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?

"Runs outside batch mode" is a real usage constraint that tells an agent not to call this inside BatchBegin/BatchEnd. However, it gives no guidance on when to prefer this over UpdateDataElement, or on the prerequisite sequence of create-then-activate that the sibling set implies.

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