Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetTransport

Retrieve ABAP transport request details from SAP by transport number to inspect metadata, status, tasks, and included objects for review or troubleshooting.

Instructions

[read-only] Retrieve ABAP transport request information including metadata, included objects, and status from SAP system. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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": {
      "transport_number": "<transport_number>"
    },
    "name": "GetTransport"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_tasksNoInclude list of tasks in transport (default: true)
include_objectsNoInclude list of objects in transport (default: true)
transport_numberYesTransport request number, not a task

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv16.0.0
    • changedInput schema / properties / transport_number / description
      Previous value: -"Transport request number (e.g., E19K905635, DEVK905123)"New value: +"Transport request number, not a task"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden, and it does well: it flags read-only semantics and, more unusually, documents the batch ('Recordable') mode where the call records a slot with empty content that must be read by number afterwards. That is real behavioral context that would otherwise be invisible. Missing only permission/authorization notes.

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?

Two tight sentences with the core purpose front-loaded, followed by the batch-mode caveat. No filler; the batch note is dense but earns its place by preventing a misinterpretation of empty responses.

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

Completeness4/5

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

For a 3-parameter read tool with no output schema, the description names what is returned (metadata, objects, status) and explains the batch-mode empty-answer behavior. An agent has enough to call it and interpret the response, with only authorization context absent.

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 per-parameter meaning (transport_number not a task, include_tasks/include_objects defaults) is already documented in the schema. The description only loosely echoes 'included objects' and adds no new syntax or format detail, so baseline 3 applies.

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?

States a specific verb and resource — retrieve ABAP transport request information (metadata, included objects, status) — which is clearly distinct from ListTransports, ReadTransportObjects, and ReadTransportActionLog. It does not explicitly name or contrast with those siblings, keeping it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the required transport_number ('not a task'), so an agent can infer this is the per-transport lookup versus a list operation. But there is no explicit when-to-use/when-not guidance or reference to alternatives like ListTransports or ReadTransportObjects.

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

Deploy Server

Other Tools