Skip to main content
Glama

UpdateDomain

Updates an existing ABAP domain by replacing all parameters, acquiring lock, performing syntax check, and optionally activating.

Instructions

Update an existing ABAP domain in SAP system.

Workflow:

  1. Acquires lock on the domain

  2. Updates domain with provided parameters (complete replacement)

  3. Performs syntax check

  4. Unlocks domain

  5. Optionally activates domain (default: true)

  6. Returns updated domain details

Note: All provided parameters completely replace existing values. Use GetDomain first to see current values if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lengthNoField length (max depends on datatype)
activateNoActivate domain after update (default: true)
datatypeNoData type: CHAR, NUMC, DATS, TIMS, DEC, INT1, INT2, INT4, INT8, CURR, QUAN, etc.
decimalsNoDecimal places (for DEC, CURR, QUAN types)
lowercaseNoAllow lowercase input
descriptionNoNew domain description (optional)
domain_nameYesDomain name to update (e.g., ZZ_TEST_0001)
sign_existsNoField has sign (+/-)
value_tableNoValue table name for foreign key relationship
fixed_valuesNoArray of fixed values for domain value range
package_nameYesPackage name (e.g., ZOK_LOCAL, $TMP for local objects)
conversion_exitNoConversion exit routine name (without CONVERSION_EXIT_ prefix)
transport_requestNoTransport request number (e.g., E19K905635). Required for transportable packages.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It details a clear workflow (lock, complete replacement, syntax check, unlock, optional activation) and explicitly states that all parameters completely replace existing values. This is comprehensive but lacks mention of error handling or side effects.

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?

The description is concise: a single-sentence purpose, a numbered 6-step workflow, and one note. Every sentence serves a purpose, and the structure is logical and front-loaded with key information.

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 13 parameters and no output schema, the description provides a good overview including the full update process. It mentions returning updated domain details but does not specify the format. It could mention prerequisites (e.g., domain must exist) but is largely complete for the 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?

Schema description coverage is 100%, so the baseline is 3. The description adds context that parameters completely replace existing values, but does not elaborate on individual parameters beyond what the schema provides. The note about using GetDomain adds minor value.

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 'Update an existing ABAP domain in SAP system,' providing a specific verb (update) and resource (ABAP domain). This distinguishes it from siblings like CreateDomain, DeleteDomain, and GetDomain, which have different purposes.

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

Usage Guidelines4/5

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

The description advises using GetDomain first to see current values, offering contextual guidance. However, it does not explicitly state when not to use this tool or contrast it with other update tools, though the specificity to domains implicitly narrows usage.

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

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