Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

get_transport_info

Check transport info and lock status for an ABAP object. Provide the object URI and development class to retrieve available transports and lock details.

Instructions

Check transport info for an ABAP object. Returns available transports and lock status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYesObject URI (e.g. /sap/bc/adt/programs/programs/ztest)
devclassYesDevelopment class/package (e.g. ZPACKAGE)
operationNoOperation (default: I_CTS_OBJECT_CHECK)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • The actual implementation of getTransportInfo — the method on AdtClient that constructs an XML payload with OPERATION, DEVCLASS, and URI, then POSTs to /sap/bc/adt/cts/transportchecks to check transport info for an ABAP object.
      async getTransportInfo(uri: string, devclass: string, 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>
          <URI>${this.escapeXml(uri)}</URI>
        </DATA>
      </asx:values>
    </asx:abap>`;
        return (await this.postWithCsrf(
          "/sap/bc/adt/cts/transportchecks",
          xml,
          "*/*",
          "application/vnd.sap.as+xml; charset=UTF-8; dataname=com.sap.adt.transport.service.checkData"
        )).data as string;
      }
  • The tool handler in the CallToolRequestSchema switch case that parses args with TransportInfoSchema and calls client.getTransportInfo(uri, devclass, operation).
    case "get_transport_info": {
      const { uri, devclass, operation } = TransportInfoSchema.parse(args);
      const result = await client.getTransportInfo(uri, devclass, operation);
      return { content: [{ type: "text", text: result }] };
    }
  • The TransportInfoSchema Zod schema defining input validation for get_transport_info (uri, devclass, optional operation).
    const TransportInfoSchema = z.object({
      uri: z.string(),
      devclass: z.string(),
      operation: z.string().optional(),
    });
  • Registration of the get_transport_info tool in the ListToolsRequestSchema handler, with description and input schema.
    {
      name: "get_transport_info",
      description: "Check transport info for an ABAP object. Returns available transports and lock status.",
      inputSchema: {
        type: "object" as const,
        properties: {
          uri: { type: "string", description: "Object URI (e.g. /sap/bc/adt/programs/programs/ztest)" },
          devclass: { type: "string", description: "Development class/package (e.g. ZPACKAGE)" },
          operation: { type: "string", description: "Operation (default: I_CTS_OBJECT_CHECK)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["uri", "devclass"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only mentions returns but does not state side effects, mutability, or required authorizations. The 'check' verb implies read-only, but this is not explicit.

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

Conciseness5/5

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

Single sentence with no extraneous information. Every word earns its place.

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?

Despite having no output schema and no annotations, the description is too brief. It fails to explain return format, interpretation of lock status, or the significance of the four parameters, especially with two required ones.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional semantic value beyond what the schema already provides.

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 clearly states the verb 'check' and the resource 'transport info for an ABAP object', and mentions returns ('available transports and lock status'). However, it does not distinguish from sibling tools like 'get_transport' or 'list_user_transports'.

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 on when to use this tool versus alternatives. The description omits any context about prerequisites or preferred scenarios.

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