ABAP-ADT-API MCP-Server

transportRelease

Release ABAP transport requests to move changes between systems. Specify a transport number and optionally bypass locks or ATC checks when needed.

Instructions

Releases a transport.

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": "transportRelease"
  }
}

Input Schema

Name	Required	Description
`transportNumber`	Yes	The transport number.
`ignoreLocks`	No	Whether to ignore locks.
`IgnoreATC`	No	Whether to ignore ATC checks.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Mar 20, 2026

TDQS

C2.4/5.0

Behavior1/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'Releases a transport' and does not mention effects, side effects, permissions, reversibility, or any other behavioral traits, making it completely transparent about the operation's implications.

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

Conciseness2/5

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

The description is a single sentence and extremely concise, but it is under-specified rather than appropriately sized. For a tool with three parameters, no annotations, and no output schema, this brevity does not serve the agent well; it lacks critical information.

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

Completeness1/5

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

This is a mutation tool with no annotations, no output schema, and a very terse description. It fails to provide essential context such as when to use it, what side effects occur, or what the return value is, making it completely inadequate for an agent to invoke correctly.

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?

The input schema provides descriptions for all three parameters (transportNumber, IgnoreATC, ignoreLocks), giving 100% schema coverage. The description adds no parameter-specific information, but the baseline of 3 is appropriate since the schema already documents the parameters fully.

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 'Releases a transport' uses a specific verb and resource, clearly indicating the action on a transport. However, it lacks context about what 'release' entails and does not distinguish it from sibling tools like transportDelete or transportSetOwner, though 'release' is distinct enough.

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 is provided on when to use this tool versus alternatives. The description only states the action without any context, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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

Deploy Server