Skip to main content
Glama

CreatePackage

Create a new ABAP package for organizing development objects in SAP systems. Define package name, parent package, and optional transport details.

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
descriptionNoPackage description. If not provided, package_name will be used.
package_nameYesPackage name (e.g., ZOK_TEST_0002). Must follow SAP naming conventions (start with Z or Y for customer namespace).
package_typeNoPackage type: 'development' (default) or 'structure'development
super_packageYesParent package name (e.g., ZOK_PACKAGE). Required for structure packages.
record_changesNoEnable change recording for the package. Required for transportable packages. Default: false.
transport_layerNoTransport layer (e.g., ZE19). Required for transportable packages.
transport_requestNoTransport request number (e.g., E19K905635). Required if package is transportable.
software_componentNoSoftware component (e.g., HOME, ZLOCAL). If not provided, SAP will set a default (typically ZLOCAL for local packages).
application_componentNoApplication component (optional, e.g., BC-ABA)
Behavior2/5

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

No annotations provided, and the description only says 'Create' without disclosing any behavioral traits such as side effects, authorization requirements, error handling (e.g., duplicate package), or the nature of the operation (idempotent/not).

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?

The description is short (two sentences) and front-loaded with the core action. However, it could be slightly more structured with a clearer separation of purpose and usage.

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 9 parameters, no output schema, and no annotations, the description lacks important context: no mention of return values, prerequisite steps, or behavioral specifics. It fails to fully inform an agent about what happens when calling this tool.

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 explains each parameter's meaning. The tool description adds no additional parameter information, earning a baseline score.

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 clearly states 'Create a new ABAP package' with a specific verb and resource. It distinguishes itself from sibling creation tools which target different object types (e.g., CreateClass, CreateTable).

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 guidance on when to use this tool versus alternatives, no prerequisites or context (e.g., needing a transport request beforehand), and no mention of when not to use it.

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/ChinhHN-DEV/abap-mcp-adt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server