Skip to main content
Glama
Hollway

mcp-abap-abap-adt-api

by Hollway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

userTransports

Read-only

List and filter a user's transport requests by owner, status, number, or description, with optional task details and target systems.

Instructions

List a user's transport requests. Returns a flat, filterable list of requests (number, description, owner, status D=modifiable/R=released, target); pass raw=true for the full ADT payload, which with targets=true can exceed 400k characters. Note that targets=false makes the backend answer with empty lists on some systems, so leave it on unless you know otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn the unfiltered ADT structure instead of the flat list.
userYesThe user.
ownerNoKeep only requests owned by this user (case-insensitive).
statusNoKeep only requests with this status: "D" (modifiable), "R" (released) or "all" (default).
targetsNoWhether to include target systems. Defaults to true, because false has been seen to return empty lists for users whose requests demonstrably exist.
numberLikeNoKeep only requests whose number contains this text, e.g. "DEVK9A3".
includeTasksNoInclude the tasks inside each request (Development/Correction entries). Off by default - they triple the output and are rarely what you are looking for.
descriptionLikeNoKeep only requests whose description contains this text (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and non-destructive, and the description adds substantial behavioral context beyond that: the raw ADT payload can exceed 400k characters, targets=false can break on some systems, and the flat list shape. This is strong disclosure of system quirks and output behavior.

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?

Three dense sentences with no filler. The core purpose is front-loaded, and each additional sentence carries a useful caveat or behavioral note that an agent needs before calling the tool.

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?

Despite having no output schema, the description enumerates the flat list fields and explains the raw/targets behaviors, giving an agent enough to understand return shape and risks. For a read-only listing tool with 100% parameter documentation, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful extra context for raw and targets—payload size and a backend caveat—while also characterizing the default flat list. This goes beyond the schema without needing to re-document every parameter.

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 opens with a specific verb and resource: 'List a user's transport requests.' It names the returned fields and status semantics, making the tool's scope unambiguous against siblings like transportDetails or transportsByConfig.

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

Usage Guidelines4/5

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

The description gives clear operational guidance: when to pass raw=true, how large the payload can get, and that targets=false can cause empty results. It does not explicitly name sibling alternatives, but the purpose is clear enough that an agent can infer when this tool applies.

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