Skip to main content
Glama

Manage Transport Requests

manage_transport_requests
Destructive

List, inspect, create, release, delete, or reassign ownership of SAP transport requests individually; use it to handle one request at a time with CTS authorization.

Instructions

Work with one transport request at a time through action: list (a user's open requests), details (header, tasks and objects of a request), create, release, delete, change_owner. release exports the request and cannot be undone; delete fails while SAP still holds object locks on it; create and change_owner change the CTS. Use list_all_transports to see other users' requests, get_transport_for_object for the request an object needs, and transport_move to move objects between requests. Needs CTS authorization (S_TRANSPRT).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_transport_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYeslist needs no transport number; details, release, delete and change_owner need transportNumber; create needs objectUrl, description and packageName; change_owner also needs newOwner
newOwnerNochange_owner only: SAP user who becomes the owner
usernameNolist only: whose open requests to show (default: the connected user)
objectUrlNocreate only: ADT URL of an object (e.g. /sap/bc/adt/programs/programs/ZREPORT) that the new request is created for
descriptionNocreate only: short text of the new request
packageNameNocreate only: package of that object (e.g. ZORDER_API)
connectionIdNoSAP system connection ID
transportNumberNoRequest number for details, release, delete and change_owner (e.g. DEVK900123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.16.2
    • changedInput schema / properties / action / description
      Previous value: -"Action to perform"New value: +"list needs no transport number; details, release, delete and change_owner need transportNumber; create needs objectUrl, description and packageName; change_owner also needs newOwner"
    • changedInput schema / properties / description / description
      Previous value: -"Description for new transport (create action)"New value: +"create only: short text of the new request"
    • changedInput schema / properties / newOwner / description
      Previous value: -"New owner username for change_owner action"New value: +"change_owner only: SAP user who becomes the owner"
    • changedInput schema / properties / objectUrl / description
      Previous value: -"Object ADT URL (create action — determines target system)"New value: +"create only: ADT URL of an object (e.g. /sap/bc/adt/programs/programs/ZREPORT) that the new request is created for"
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name for new transport (create action)"New value: +"create only: package of that object (e.g. ZORDER_API)"
    • changedInput schema / properties / transportNumber / description
      Previous value: -"Transport number for details / release / delete / change_owner (e.g. DEVK123456)"New value: +"Request number for details, release, delete and change_owner (e.g. DEVK900123)"
    • changedInput schema / properties / username / description
      Previous value: -"Username for list action (defaults to current user)"New value: +"list only: whose open requests to show (default: the connected user)"
  2. First observedv1.16.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (destructive, openWorld, non-idempotent), it discloses that release exports and cannot be undone, that delete fails while SAP holds object locks, that create/change_owner mutate CTS state, and that CTS authorization (S_TRANSPRT) is required. These are concrete behavioral consequences an agent cannot get from the annotation flags.

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?

One dense, front-loaded paragraph where nearly every clause carries new information. The action-requirement mapping mildly duplicates the schema's action enum description, which is the only redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, non-idempotent, destructive multi-action tool with no output schema, it covers authorization, irreversibility, and a key failure mode, plus sibling routing. Return content is only hinted at ('header, tasks and objects'), which is a minor gap given no output schema exists to document it.

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 documents every parameter and its per-action requirement. The description's parameter guidance ('list needs no transport number...') largely restates the action enum's own description, adding no format or constraint detail beyond the schema. Baseline 3 applies.

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 opens with a specific verb+resource and enumerates all six actions (list, details, create, release, delete, change_owner), so an agent knows exactly what the tool does without opening the schema. It is clearly separable from siblings such as list_all_transports and transport_move.

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?

It explicitly routes the agent: use list_all_transports for other users' requests, get_transport_for_object for an object's required request, and transport_move to move objects. The scope constraint 'one transport request at a time' plus the per-action routing leaves nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.