Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

release_transport

Release a transport request for import into SAP target systems. Specify the transport number and optionally the system ID to initiate the release.

Instructions

Release a transport request for import into target systems

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transport_numberYesTransport number (e.g. DEVK900123)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Tool registration in the ListToolsRequestSchema handler — defines the 'release_transport' tool with its input schema (transport_number required + optional system_id).
    {
      name: "release_transport",
      description: "Release a transport request for import into target systems",
      inputSchema: {
        type: "object" as const,
        properties: {
          transport_number: { type: "string", description: "Transport number (e.g. DEVK900123)" },
          ...SYSTEM_ID_PROP,
        },
        required: ["transport_number"],
      },
    },
  • Zod schema for transport number input validation, used by both get_transport, release_transport, and delete_transport handlers.
    const TransportNumberSchema = z.object({ transport_number: z.string() });
  • Handler in the CallToolRequestSchema switch statement — parses the transport_number argument and delegates to client.releaseTransport().
    case "release_transport": {
      const { transport_number } = TransportNumberSchema.parse(args);
      const result = await client.releaseTransport(transport_number);
      return { content: [{ type: "text", text: result }] };
    }
  • Actual implementation in AdtClient — POSTs to ADT CTS endpoint /newreleasejobs with an empty body to trigger transport release.
    async releaseTransport(transportNumber: string): Promise<string> {
      return (await this.postWithCsrf(
        `/sap/bc/adt/cts/transportrequests/${encodeURIComponent(transportNumber.toUpperCase())}/newreleasejobs`,
        "",
        "*/*"
      )).data as string;
    }
Behavior2/5

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

The description is minimal and does not disclose behavioral traits beyond the action of releasing. With no annotations, it fails to specify side effects, required permissions, or whether the action is reversible.

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, efficient sentence with no unnecessary words, which is beneficial for quick parsing. However, it could include more detail without becoming verbose.

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?

For a mutation tool with no output schema and no annotations, the description lacks critical context about expected results, error conditions, and what 'release' entails, making it incomplete.

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% and the description adds no additional meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate as the schema already documents the parameters adequately.

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 the action 'release' on the resource 'transport request', with a specific purpose 'for import into target systems'. This distinguishes it from sibling tools like 'create_transport' or 'delete_transport'.

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, such as when a transport must be released before import or any prerequisites like user authorization.

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