Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateDomain

Creates a new ABAP domain in an SAP system with configurable data type, length, fixed values, and optional activation to define reusable field attributes.

Instructions

Create a new ABAP domain in SAP system. Creates the domain object in initial state. Runs outside batch mode.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain_name": "<domain_name>"
    },
    "name": "CreateDomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
lengthNo(optional) Field length (max depends on datatype)
activateNo(optional) Activate domain after creation (default: true)
datatypeNo(optional) Data type: CHAR, NUMC, DATS, TIMS, DEC, INT1, INT2, INT4, INT8, CURR, QUAN, etc.CHAR
decimalsNo(optional) Decimal places (for DEC, CURR, QUAN types)
lowercaseNo(optional) Allow lowercase input
descriptionNo(optional) Domain description. If not provided, domain_name will be used.
domain_nameYesDomain name.
sign_existsNo(optional) Field has sign (+/-)
value_tableNo(optional) Value table name for foreign key relationship
fixed_valuesNo(optional) Array of fixed values for domain value range
package_nameNo(optional) Package name
conversion_exitNo(optional) Conversion exit routine name (without CONVERSION_EXIT_ prefix)
master_languageNoOptional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
transport_requestNo(optional) Transport request number, not a task. Required for transportable packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv16.0.0
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / domain_name / description
      Previous value: -"Domain name (e.g., ZZ_TEST_0001). Must follow SAP naming conventions."New value: +"Domain name."
    • changedInput schema / properties / package_name / description
      Previous value: -"(optional) Package name (e.g., ZOK_LOCAL, $TMP for local objects)"New value: +"(optional) Package name"
    • changedInput schema / properties / transport_request / description
      Previous value: -"(optional) Transport request number (e.g., E19K905635). Required for transportable packages."New value: +"(optional) Transport request number, not a task. Required for transportable packages."
  2. Changed1 schema field changedv8.1.0
    • addedInput schema / properties / master_language
      Added value: +{
+  "description": "Optional master/original language for the created object (e.g. \"EN\", \"DE\", \"ZH\"). Defaults to the session language (SAP_LANGUAGE) or EN.",
+  "type": "string"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the domain is created in initial state and that it runs outside batch mode, but it omits permissions, transport behavior, idempotency, failure modes, and what happens when activation is enabled by default.

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 three short sentences with no filler, and the core action is front-loaded. The initial-state and batch-mode notes are relevant and compact.

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?

This is a 15-parameter mutation tool with no annotations and no output schema, yet the description is very thin. The schema covers parameters well, but the description does not explain return behavior, lifecycle implications, or key creation prerequisites, leaving important context gaps.

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 15 parameters in detail. The description adds no parameter-specific semantics beyond the action itself, which meets the baseline for fully covered schemas but does not add extra guidance.

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 states a specific verb and resource: 'Create a new ABAP domain in SAP system.' It distinguishes creation from sibling operations such as UpdateDomain, ActivateDomain, and DeleteDomain by specifying that the object is created 'in initial state.'

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 this is for creating a new domain, and 'Runs outside batch mode' gives one execution constraint. However, it does not explicitly say when to use this instead of UpdateDomain or ActivateDomain, nor does it state prerequisites or exclusions beyond batch mode.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools