mcp-abap-abap-adt-api

transportDelete

Destructive

Delete an open, empty transport request or task. Use to remove a transport without touching its objects. Released requests cannot be deleted; action is irreversible.

Instructions

Delete a transport request or a task inside it. Only works while it is still open and empty of anything you want to keep: the objects in it stay as they are, only the request goes. Released requests cannot be deleted at all. Not undoable - ask before doing it to a request you did not create.

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": {
      "transportNumber": "<transportNumber>"
    },
    "name": "transportDelete"
  }
}

Input Schema

Name	Required	Description	Default
`transportNumber`	Yes	The transport number.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4/5.0

Behavior5/5

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

Far beyond the destructiveHint annotation, the description discloses that deletion is not undoable, only works on open empty containers, preserves contained objects, and fails on released requests. This gives an agent a concrete behavioral model of the side effects and constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The opening sentence is front-loaded and the warnings are relevant, but the second sentence ('Only works...') is convoluted and can read as contradictory ('empty of anything you want to keep' vs. 'objects in it stay as they are'). The content is useful but needs tightening.

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 a one-parameter destructive tool with no output schema, the description covers preconditions, side effects, non-undoability, and ownership caution. It leaves minor ambiguity about how a task deletion behaves versus a request deletion, so it is not a perfect 5.

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 coverage is 100% for the single transportNumber parameter, so the baseline is 3. The description reinforces that the number may refer to a request or a task, but it does not state how task versus request is distinguished or the expected format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action 'Delete' and the resource 'a transport request or a task inside it', and the opening sentence is specific enough that an agent can tell it apart from release or owner-change siblings. It does not explicitly name a sibling to differentiate from, so it stops short of a 5.

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?

It gives explicit preconditions and exclusions: only open requests, not released requests, and not undoable, with a caution to ask before deleting requests the user did not create. It does not point to an alternative tool when deletion is not possible, so it is not a full 5.

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

Deploy Server