Skip to main content
Glama

List All Transports

list_all_transports
Read-onlyIdempotent

Lists transport requests across all users or a single owner, grouped by owner and newest first, with status, date, description and optional objects.

Instructions

List transport requests of all users (or one owner), grouped by owner and newest first: number, kind, status, date, description, the piece of work it is remembered for, and optionally its objects including its tasks' objects. Reads the CTS tables E070, E07T and E071 with SQL through ADT, so it needs table read authorization (S_TABU_DIS). Use manage_transport_requests with list for one user's open requests and details for a single request. Read-only; at most 500 requests, objects for the newest 100.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_all_transports"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoOnly this SAP user's requests (e.g. DEVELOPER1); default: all users
statusNoWhich transports to show: modifiable (default, open/unreleased), released, or all
withObjectsNoList the objects in each request (default true; newest 100 requests)
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.2
    • changedInput schema / properties / owner / description
      Previous value: -"Only this user's requests"New value: +"Only this SAP user's requests (e.g. DEVELOPER1); default: all users"
  2. First observedv1.16.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the underlying tables (E070, E07T, E071), that access goes through ADT with SQL, the required authorization object S_TABU_DIS, and hard caps of 500 requests with objects only for the newest 100. Those are operational facts an agent cannot get from annotations or schema.

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?

Front-loaded with the purpose and result shape, then prerequisites, then the sibling routing. Dense but every clause carries information; the single very long opening sentence is the only readability cost.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the returned fields and the optional nested objects. Authorization requirements, row caps, and the sibling alternative are all present, leaving nothing essential for a correct call unstated.

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%, so all four parameters, including the status enum and withObjects default, are already documented. The description hints at the objects/tasks-objects payload and the 100-request object limit, but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (list transport requests), the scope (all users or one owner), the ordering (grouped by owner, newest first), and the fields returned. The final sentence explicitly distinguishes it from manage_transport_requests.

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

Usage Guidelines5/5

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

Names the alternative tool and the exact conditions that select it: 'manage_transport_requests with list for one user's open requests and details for a single request.' It also clarifies the owner parameter's role as a narrowing filter rather than a replacement.

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