Skip to main content
Glama

UpdateDomain

Update an ABAP domain by replacing its attributes. The tool locks the domain, applies changes, unlocks, and can activate the domain.

Instructions

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

Input Schema

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

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

The description discloses that the tool locks, performs a complete replacement update, unlocks, and optionally activates. This provides useful behavioral context. However, it does not clarify what happens to parameters not provided (e.g., whether they are cleared or retained) or the exact effects of locking/unlocking.

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 four sentences, but the opening 'Operation: Update, Create' is somewhat redundant and could be removed. It includes necessary behavioral information but could be more streamlined.

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's complexity with 13 parameters and no output schema, the description lacks details on return values, error handling, and the effect on unspecified parameters. For a tool that potentially creates domains, the description should clarify the creation scenario more explicitly.

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?

All 13 parameters are described in the input schema with full coverage. The description adds no additional parameter semantics beyond the schema. With high schema coverage, a baseline of 3 is appropriate.

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 states that the tool updates an existing ABAP domain, with specification of locking, replacement, unlocking, and activation. However, it also ambiguously mentions 'Operation: Update, Create,' suggesting it might also create domains, which may confuse the agent. It distinguishes from siblings like CreateDomain and ActivateDomain by focusing on update behavior.

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?

The description only vaguely states 'will be useful for updating or creating domain' without providing explicit guidance on when to use this tool versus alternatives like CreateDomain or CheckDomain. No conditions or prerequisites are mentioned.

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