Skip to main content
Glama
abap0917

abap-adt-mcp

by abap0917

adt_create_package

Create an ABAP development package nested under an existing parent package. Automatically inherits software component and transport layer from the parent, with optional overrides.

Instructions

Create a development package (DEVC/K). A package must nest under an existing parent package and inherit that parent's software component + transport layer, so pass superPackage (a real customer package, e.g. ZRAP_TEST_192637 — NOT $TMP). softwareComponent/transportLayer are derived from the parent automatically; pass them explicitly only to override. Name must match the Z*/Y* prefix. Returns the package URI and the resolved attributes. NOTE: this is the 'create package' branch of the package/transport decision flow — use it when a write tool returns a package clarification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPackage (devclass) name, e.g. ZMY_PKG. Must match Z*/Y* prefix. REQUIRED — if omitted, the tool returns a clarification listing what to collect from the user.
transportNoTransport request for the creation (parent is non-$TMP, so usually required).
descriptionNoShort text / description. REQUIRED.
packageTypeNoPackage type. Default 'development'.
superPackageNoParent package to nest under, e.g. ZRAP_TEST_192637. Must be a real package (not $TMP); its softwareComponent/transportLayer are inherited. REQUIRED.
transportLayerNoOverride transport layer (e.g. ZS4C). Default: inherited from superPackage.
softwareComponentNoOverride software component (e.g. HOME). Default: inherited from superPackage.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses nesting inheritance, automatic derivation of software component/transport layer, option to override, and return value (URI + resolved attributes). No mention of destructive behavior or auth, but appropriate for a create tool.

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?

Approximately 5 sentences, well-structured with main action first, then constraints, then parameter clarifications. Slightly dense but not overly verbose; a minor simplification could improve conciseness.

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?

Given no output schema, description explains return value. All 7 parameters are covered with context. Sibling tools are diverse (ABAP development), and this description clearly differentiates the package creation step. Complete for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds meaning beyond schema: clarifies superPackage must be real, softwareComponent/transportLayer inheritance, and naming prefix requirement. This adds value for agent understanding.

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 the tool creates a development package (DEVC/K) with specific verb 'Create' and resource 'development package'. It distinguishes from siblings by referencing the 'package/transport decision flow' and specifying it's the 'create package' branch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use: when a write tool returns a package clarification. Provides constraints: parent must be real (not $TMP), naming prefix Z*/Y*, and clarifies inheritance and override conditions.

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

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