Skip to main content
Glama

UpdateDataElement

Update or create an ABAP data element with specified parameters, including locking, unlocking, and optional activation.

Instructions

Operation: Update, Create. Subject: DataElement. Will be useful for updating or creating data element. Update an existing ABAP data element. Locks, updates with provided parameters (complete replacement), unlocks, and optionally activates.

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)
Behavior3/5

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

The description discloses the process (locks, updates with complete replacement, unlocks, optionally activates) but lacks detail on authorization requirements, side effects on dependent objects, or return values. With no annotations, more depth would be beneficial.

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

Conciseness3/5

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

The description is somewhat repetitive and fragmented (e.g., 'Operation: Update, Create' then 'update an existing'). Could be more concise and better structured for quick reading.

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

Completeness2/5

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

Given the tool has 17 parameters and no output schema, the description does not explain return values or when to use create vs update. The process description is helpful but insufficient for a tool of this complexity.

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?

Input schema has 100% description coverage, so the description adds little beyond the schema. Baseline 3 is appropriate; the description does not clarify parameter interplay or provide examples.

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 clearly identifies the tool as updating an existing ABAP data element, using the verb 'Update' and specifying the subject. It differentiates from CreateDataElement among siblings, though there is slight ambiguity about create vs update.

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?

No explicit guidance on when to use this tool versus alternatives like CreateDataElement or other update tools. No prerequisites mentioned beyond the input schema's required fields.

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