Skip to main content
Glama

CreatePackage

Create a new ABAP package to organize development objects in SAP systems. Provide package name and parent package to set up the container.

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
package_nameYesPackage name (e.g., ZOK_TEST_0002). Must follow SAP naming conventions (start with Z or Y for customer namespace).
descriptionNoPackage description. If not provided, package_name will be used.
super_packageYesParent package name (e.g., ZOK_PACKAGE). Required for structure packages.
package_typeNoPackage type: 'development' (default) or 'structure'development
software_componentNoSoftware component (e.g., HOME, ZLOCAL). If not provided, SAP will set a default (typically ZLOCAL for local packages).
transport_layerNoTransport layer (e.g., ZE19). Required for transportable packages.
transport_requestNoTransport request number (e.g., E19K905635). Required if package is transportable.
record_changesNoEnable change recording for the package. Required for transportable packages. Default: false.
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; description only states creation with no details on side effects, required authorizations, or system impacts.

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?

Two efficient sentences, front-loaded with action and resource, providing just enough context without redundancy.

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?

Adequate for a simple creation tool but lacks explanation of return values and behavioral details given no output schema and 9 parameters.

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 covers all 9 parameters with descriptions; description adds no extra parameter information beyond the contextual sentence about packaging.

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?

Description clearly states the tool creates a new ABAP package and explains the resource type, distinguishing from sibling Create tools for other objects.

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 vs other Create tools, no prerequisites or exclusions provided.

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