Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

create_transport

Create a new transport request in an SAP system by specifying a development class and description. This tool enables automated transport request creation for ADT-managed SAP objects.

Instructions

Create a new transport request in the SAP system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devclassYesDevelopment class/package (e.g. ZPACKAGE)
descriptionYesTransport description text
refNoObject reference URI
operationNoOperation (default: I_CTS_OBJECT_CHECK)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Core handler: AdtClient.createTransport() that builds an XML request and POSTs to /sap/bc/adt/cts/transports to create a transport request.
      async createTransport(devclass: string, description: string, ref = "", operation = "I_CTS_OBJECT_CHECK"): Promise<string> {
        const xml = `<?xml version="1.0" encoding="UTF-8"?>
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
      <asx:values>
        <DATA>
          <OPERATION>${this.escapeXml(operation)}</OPERATION>
          <DEVCLASS>${this.escapeXml(devclass)}</DEVCLASS>
          <REQUEST_TEXT>${this.escapeXml(description)}</REQUEST_TEXT>
          <REF>${this.escapeXml(ref)}</REF>
        </DATA>
      </asx:values>
    </asx:abap>`;
        return (await this.postWithCsrf(
          "/sap/bc/adt/cts/transports",
          xml,
          "*/*",
          "application/vnd.sap.as+xml; charset=UTF-8; dataname=com.sap.adt.transport.service.createData"
        )).data as string;
      }
  • MCP tool handler for 'create_transport': parses args using CreateTransportSchema and delegates to AdtClient.createTransport()
    case "create_transport": {
      const { devclass, description, ref, operation } = CreateTransportSchema.parse(args);
      const result = await client.createTransport(devclass, description, ref, operation);
      return { content: [{ type: "text", text: result }] };
    }
  • Zod schema for create_transport input validation (devclass, description, ref, operation)
    const CreateTransportSchema = z.object({
      devclass: z.string(),
      description: z.string(),
      ref: z.string().optional(),
      operation: z.string().optional(),
    });
  • Tool registration in ListToolsRequestSchema handler, defining the create_transport tool with its input schema
    {
      name: "create_transport",
      description: "Create a new transport request in the SAP system",
      inputSchema: {
        type: "object" as const,
        properties: {
          devclass: { type: "string", description: "Development class/package (e.g. ZPACKAGE)" },
          description: { type: "string", description: "Transport description text" },
          ref: { type: "string", description: "Object reference URI" },
          operation: { type: "string", description: "Operation (default: I_CTS_OBJECT_CHECK)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["devclass", "description"],
      },
    },
  • Tool dispatch in CallToolRequestSchema handler routing 'create_transport' to the implementation
    case "create_transport": {
      const { devclass, description, ref, operation } = CreateTransportSchema.parse(args);
      const result = await client.createTransport(devclass, description, ref, operation);
      return { content: [{ type: "text", text: result }] };
    }
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details. It does not disclose whether the tool requires specific authorizations, what happens on failure, or if it has any side effects. The description is too minimal to inform the agent about the tool's behavior beyond the basic action.

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 sentence that is concise and to the point. However, it is slightly too brief; adding a sentence about typical usage or return value would improve structure without sacrificing 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?

Given the complexity of 5 parameters (2 required), no output schema, and no annotations, the description is incomplete. It does not explain what the tool returns (e.g., the new transport number), nor does it address important behavioral details. The minimal information leaves the agent under-informed for proper usage.

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?

Input schema has 100% description coverage with clear parameter descriptions (e.g., default for 'operation', examples for 'devclass'). The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'Create a new transport request in the SAP system', using a specific verb ('create') and resource ('transport request'). This distinguishes it from sibling tools like 'delete_transport', 'release_transport', and 'list_user_transports', providing clear purpose.

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. There is no mention of prerequisites, when not to use it, or any comparison to sibling tools. For example, it does not indicate that 'release_transport' should be used after creating a transport, leaving the agent without context for proper workflow sequencing.

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/ethanhan2014/sap-adt-mcp'

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