Skip to main content
Glama

UpdateDataElement

Modify an existing ABAP data element in SAP systems by updating its type, description, labels, and technical properties. This tool handles locking, complete replacement of parameters, and optional activation.

Instructions

Update an existing ABAP data element in SAP system.

Workflow:

  1. Gets domain info (if type_kind is 'domain') to extract dataType/length/decimals

  2. Acquires lock on the data element

  3. Updates data element with provided parameters (complete replacement)

  4. Unlocks data element

  5. Optionally activates data element (default: true)

  6. Returns updated data element details

Supported type_kind values:

  • domain: Based on ABAP domain (requires type_name = domain name)

  • predefinedAbapType: Direct ABAP type (requires data_type, length, decimals)

  • refToPredefinedAbapType: Reference to ABAP type (requires data_type, length, decimals)

  • refToDictionaryType: Reference to another data element (requires type_name = data element name)

  • refToClifType: Reference to class (requires type_name = class name)

Note: All provided parameters completely replace existing values. Field labels are truncated to max lengths (10/20/40/55).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_element_nameYesData element name to update (e.g., ZZ_TEST_DTEL_01)
descriptionNoNew data element description
package_nameYesPackage name (e.g., ZOK_LOCAL, $TMP for local objects)
transport_requestNoTransport request number (e.g., E19K905635). Required for transportable packages.
type_kindNoType kind: domain, predefinedAbapType, refToPredefinedAbapType, refToDictionaryType, refToClifTypedomain
type_nameNoType name: domain name, data element name, or class name (depending on type_kind)
data_typeNoData type (CHAR, NUMC, etc.) - for predefinedAbapType or refToPredefinedAbapType
lengthNoLength - for predefinedAbapType or refToPredefinedAbapType
decimalsNoDecimals - for predefinedAbapType or refToPredefinedAbapType
field_label_shortNoShort field label (max 10 chars)
field_label_mediumNoMedium field label (max 20 chars)
field_label_longNoLong field label (max 40 chars)
field_label_headingNoHeading field label (max 55 chars)
search_helpNoSearch help name
search_help_parameterNoSearch help parameter
set_get_parameterNoSet/Get parameter ID
activateNoActivate data element after update (default: true)
Behavior4/5

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

With no annotations provided, the description carries full burden and adds significant behavioral context: it details a multi-step workflow (lock, update, unlock, activate), notes that updates are complete replacements, mentions truncation of field labels, and specifies default activation. This goes beyond basic schema information, though it could mention permissions or error handling.

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?

The description is well-structured with a clear opening statement, numbered workflow steps, and bullet points for type_kind values. It is front-loaded with key information, though the detailed workflow and notes could be slightly condensed without losing clarity.

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 the complexity (17 parameters, no output schema, no annotations), the description provides substantial context: workflow, parameter interactions, and behavioral notes. It compensates well for the lack of structured fields, though it could include more on error cases or return values to be fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds value by explaining the dependencies between type_kind and other parameters (e.g., 'domain' requires type_name as domain name), clarifying that all parameters replace existing values, and noting field label truncation. This enhances understanding beyond the schema's parameter 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?

The description clearly states the specific action ('Update an existing ABAP data element') and resource ('in SAP system'), distinguishing it from siblings like CreateDataElement or DeleteDataElement. The title is null, but the description fully compensates with precise verb+resource identification.

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 implies usage through the workflow and type_kind details but does not explicitly state when to use this tool versus alternatives like UpdateDomain or UpdateTable. It provides context for the update process but lacks explicit guidance on prerequisites or exclusions.

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/fr0ster/mcp-abap-adt'

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