Skip to main content
Glama

SAPTransport

Manage SAP CTS transport requests: list, create, release, delete, reassign, check transport needs, and find object history.

Instructions

Manage CTS transport requests (SE09/SE10 equivalent). Actions: list (defaults to current user, modifiable transports — both Workbench and Customizing), get (details with tasks and objects), create (K=Workbench, W=Customizing, T=Transport of Copies), release, delete, reassign (change owner), release_recursive (release tasks first, then parent), check (check if a package requires a transport — provide type, name, package), history (find transports referencing an object — provide type, name; read-only, works without SAP_ALLOW_TRANSPORT_WRITES). Transport IDs look like A4HK900123. Status: D=modifiable, R=released.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYeslist: show transports (defaults to current user, modifiable only). get: fetch transport details including tasks and objects. create: create a new transport request (description required; package optional, defaults to $TMP — pass an explicit package to influence the transport route/type). release: release a single transport or task. delete: delete a transport (use recursive=true to delete tasks first). reassign: change transport owner (use recursive=true for tasks too). release_recursive: release all unreleased tasks first, then the transport itself. check: check if a transport is needed for a package/object (requires type, name, package). history: list transports referencing an object (reverse lookup; requires type, name; works without SAP_ALLOW_TRANSPORT_WRITES).
idNoTransport request ID, e.g. A4HK900123 (required for get/release/delete/reassign/release_recursive)
descriptionNoTransport description text (required for create)
nameNoObject name (for check or history actions)
packageNoPackage name. For create: optional — defaults to $TMP, pass an explicit package to influence the transport route (SAP infers K/W/T from the package's TADIR route). For check: required.
userNoSAP username to filter by (for list). Defaults to the current SAP user. Use "*" to list all users.
statusNoTransport status filter (for list). D=modifiable (default), R=released, "*"=all statuses.
typeNoObject type for check/history actions (PROG, CLAS, DDLS, etc.). Not used by create — the SAP backend infers transport type (K/W/T) from the package's TADIR route on the CreateCorrectionRequest endpoint.
ownerNoNew owner SAP username (required for reassign)
recursiveNoApply recursively to child tasks (for delete/reassign). release_recursive always recurses.
Behavior4/5

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

With no annotations, the description bears full responsibility. It discloses behaviors like defaults, transport ID format, status codes, and read-only nature of history. It implies mutation for create/release/delete but does not explicitly state destructive potential or 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.

Conciseness4/5

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

The description is dense but well-structured, starting with the main purpose and actions. It could be slightly more concise by grouping action-specific details, but the information density is high without being verbose.

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 the tool's complexity (10 parameters, many actions, no output schema), the description is comprehensive. It covers all actions, parameter roles, defaults, and special cases (e.g., history without SAP_ALLOW_TRANSPORT_WRITES). No gaps evident.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds significant value: it explains defaults (e.g., package defaults to $TMP for create), usage per action, and nuances like influence of package on transport route. This goes well beyond the schema's basic property definitions.

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 manages CTS transport requests (SE09/SE10 equivalent) and enumerates specific actions: list, get, create, release, delete, reassign, release_recursive, check, history. It distinguishes from sibling tools by targeting transport management specifically.

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

Usage Guidelines4/5

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

The description provides usage context for each action, default behaviors (e.g., list defaults to current user, modifiable transports), and conditions (e.g., history works without SAP_ALLOW_TRANSPORT_WRITES). However, it does not explicitly contrast with alternatives or state when not to use the tool.

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/marianfoo/arc-1'

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