Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreatePackage

Creates a new ABAP package in an SAP system to organize development objects. Requires package name and parent package; supports type and transport options.

Instructions

Create a new ABAP package in SAP system. Packages are containers for development objects and are essential for organizing code.

Input Schema

TableJSON 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

C2.9/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, and it discloses essentially nothing: no permission requirements, no transport/change-recording implications, no statement about whether creation is idempotent or fails on duplicate names. The second sentence is background description of ABAP packages, not behavioral context for the call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two short sentences, front-loaded with the action. The second sentence is arguably filler for an agent that already knows SAP, but it costs little and never buries the operative content.

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 mutating, 11-parameter creation tool with no annotations and no output schema, so the description should at minimum cover preconditions (transport layer/request for transportable packages) and what constitutes success or failure. It covers none of that, leaving the agent to reconstruct prerequisites from scattered schema property descriptions.

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?

With 11 parameters at 100% schema description coverage, the schema already documents each field, including the transport-related conditionals. The description adds no parameter-level meaning, so the 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?

States a specific verb and resource (create an ABAP package in an SAP system) and adds a one-line definition of what a package is. The purpose is unambiguous and separable from read-side siblings like GetPackage or GetPackageContents, though it does not explicitly name those alternatives.

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 when-to-use guidance, no prerequisites, and no mention of alternatives (e.g., CheckPackage to validate first, GetPackage to inspect an existing one). The agent must infer everything about invocation context from the name alone.

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