Skip to main content
Glama

UpdateDomain

Update an ABAP domain by replacing its properties and optionally activating it. Supports datatype, length, fixed values, and other attributes.

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
Behavior4/5

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

The description discloses key behaviors: locking, complete replacement update, unlocking, and optional activation. No annotations are provided, so the description carries the full burden, and it does so reasonably well, though it could mention error handling or prerequisites.

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 three sentences but includes redundant phrases like 'Operation: Update, Create. Subject: Domain.' and 'Will be useful for updating or creating domain.' Could be more concise without losing information.

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?

Given the tool has 13 parameters and no output schema, the description covers the update process (lock, update, unlock, activate) but lacks information on return values, error scenarios, or prerequisites. It is adequate but not fully complete.

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 schema already documents all parameters. The description adds no additional meaning or context beyond what is in the schema, resulting in baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Update an existing ABAP domain' but also mentions 'Operation: Update, Create.' leading to ambiguity since there is a sibling 'CreateDomain' tool. The 'create' reference is misleading and not aligned with the tool's primary function.

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 ActivateDomain, CheckDomain, or CreateDomain. The description does not help the agent choose correctly among multiple domain-related tools.

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