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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreatePackage

Creates a new ABAP package in an SAP system as a container for organizing development objects, with options for package type, transport layer, and change recording.

Instructions

Create a new ABAP package in SAP system. Packages are containers for development objects and are essential for organizing code. When the connection is HTTP, recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "package_name": "<package_name>",
      "super_package": "<super_package>"
    },
    "name": "CreatePackage"
  }
}

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
descriptionNoPackage description. If not provided, package_name will be used.
package_nameYesPackage name.
package_typeNoPackage type: 'development' (default) or 'structure'development
super_packageYesParent package name. Required for structure packages.
record_changesNoEnable change recording for the package. Required for transportable packages. Default: false.
master_languageNoOptional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
transport_layerNoTransport layer. Required for transportable packages.
transport_requestNoTransport request number, not a task. Required if the package is transportable.
software_componentNoSoftware component. If not provided, SAP will set a default.
application_componentNoApplication component (optional, e.g., BC-ABA)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / package_name / description
      Previous value: -"Package name (e.g., ZOK_TEST_0002). Must follow SAP naming conventions (start with Z or Y for customer namespace)."New value: +"Package name."
    • changedInput schema / properties / software_component / description
      Previous value: -"Software component (e.g., HOME, ZLOCAL). If not provided, SAP will set a default (typically ZLOCAL for local packages)."New value: +"Software component. If not provided, SAP will set a default."
    • changedInput schema / properties / super_package / description
      Previous value: -"Parent package name (e.g., ZOK_PACKAGE). Required for structure packages."New value: +"Parent package name. Required for structure packages."
    • changedInput schema / properties / transport_layer / description
      Previous value: -"Transport layer (e.g., ZE19). Required for transportable packages."New value: +"Transport layer. Required for transportable packages."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required if package is transportable."New value: +"Transport request number, not a task. Required if the package is transportable."
  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. Addedv7.0.0
  4. Removedv6.11.3
  5. Changed1 schema field changed
    • addedInput schema / properties / record_changes
      Added value: +{
+  "description": "Enable change recording for the package. Required for transportable packages. Default: false.",
+  "type": "boolean"
+}
  6. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutating tool, yet it says nothing about permissions, idempotency/duplicate handling, transportability consequences, or failure modes. The only behavioral content is a generic and awkwardly worded batch/HTTP recording note that is boilerplate about the batching subsystem rather than about this tool's 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.

Conciseness3/5

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

The purpose is correctly front-loaded in the first sentence, but nearly half the text is a convoluted sentence about HTTP/batch recording ("recorded under the next number and answers with empty content") that is hard to parse and irrelevant to most callers. That sentence costs more than it earns.

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

Completeness5/5

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

The description gives a clear tool purpose while the rich parameter schema, including transport-related parameters, fully covers inputs and expected defaults. Against a rich 11-parameter schema with 100% coverage, the description is proportionate without needing to restate parameter details.

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% and every parameter carries a meaningful description (transport_layer, transport_request, record_changes, detail, etc.), so the schema does the heavy lifting. The description adds no parameter semantics beyond that; baseline 3 applies.

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 first sentence gives a specific verb and resource ("Create a new ABAP package") plus a short gloss on what a package is. It is clearly distinguishable from GetPackage/UpdatePackage/DeletePackage by the verb, though it never explicitly contrasts with CheckPackage or explains ordering relative to those siblings.

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?

There is no statement of when to use this versus alternatives, no prerequisites (e.g. that a parent/super package or transport request must already exist for transportable packages), and no note on what to do if the package already exists. Usage must be inferred entirely from the name and schema.

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