ABAP-ADT-API MCP-Server

createTransport

Create a new transport request for ABAP objects by specifying the source URL, description, and development class. This tool enables managing ABAP development transports through the ADT API interface.

Instructions

Create a new transport request

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": {
      "objSourceUrl": "<objSourceUrl>",
      "REQUEST_TEXT": "<REQUEST_TEXT>",
      "DEVCLASS": "<DEVCLASS>"
    },
    "name": "createTransport"
  }
}

Input Schema

Name	Required	Description
`objSourceUrl`	Yes	URL of the object source
`REQUEST_TEXT`	Yes	Description of the transport request
`DEVCLASS`	Yes	Development class
`transportLayer`	No	Transport layer

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Mar 20, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It merely states 'Create' without disclosing side effects, required permissions, reversibility, or return behavior. This is insufficient for a mutation 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?

The description is a single clear sentence with no redundant information. It is appropriately brief, though it could include more detail without losing conciseness.

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

Completeness2/5

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

The tool has 4 parameters, no annotations, and no output schema. The one-sentence description does not cover prerequisites, expected behavior, or return values, leaving significant gaps for an agent to invoke it 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter meaning beyond the schema's own field descriptions, which are minimal but present.

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 'Create a new transport request' uses a specific verb and resource, clearly distinguishing it from sibling tools like createTransportsConfig (which creates transport configuration) and transportDelete/release.

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, nor any prerequisites such as login or configuration requirements. The description simply states the action without context.

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

Deploy Server