Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ListTransports

List SAP transport requests for a user or current session user, returning modifiable and released workbench and customizing requests. Filter client-side by user or modifiable-only.

Instructions

[read-only] List transport requests for the current or specified user. Returns modifiable and/or released workbench and customizing requests. user and modifiable-only are both applied client-side, over every request the server's default search configuration answers — not sent to ADT as filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoSAP user name to filter to; applied client-side. If not provided, defaults to the current session user, so an unfiltered call already answers only that user's transports.
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
modifiable_onlyNoOnly return modifiable (not yet released) transports; applied client-side. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv16.0.0
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / modifiable_only / description
      Previous value: -"Only return modifiable (not yet released) transports. Default: true."New value: +"Only return modifiable (not yet released) transports; applied client-side. Default: true."
    • changedInput schema / properties / user / description
      Previous value: -"SAP user name. If not provided, returns transports for the current user."New value: +"SAP user name to filter to; applied client-side. If not provided, defaults to the current session user, so an unfiltered call already answers only that user's transports."
  2. Added

TDQS

A4.1/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 does useful work: it self-declares read-only and, importantly, discloses that the user and modifiable-only filters are applied client-side over the server's default search configuration rather than being pushed to ADT. That is a non-obvious behavioral trait affecting result semantics and volume. It stops short of covering auth needs or result-size implications.

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-loads the read-only marker and the core purpose, then qualifies filtering behavior in two efficient sentences. Slightly dense but every sentence earns its place; no redundant fluff.

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 no-output-schema, no-annotation list tool, the description covers read-only nature, scope, filter semantics, and the kind of requests returned. It does not describe the returned fields or default result ordering, but it is complete enough to invoke correctly.

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 schema already documents all three parameters (including the client-side note). The description largely restates that filtering is client-side and adds only the nuance about the server's default search configuration, so it hovers at the baseline rather than adding real new meaning.

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?

Opens with a specific verb+resource ("List transport requests") and scopes it to the current or specified user, then narrows content to modifiable/released workbench and customizing requests. This clearly separates it from the singular GetTransport and the write-oriented CreateTransport/CreateTransportTask siblings.

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?

Gives clear context for when an unfiltered call is appropriate (defaults to the session user, so it answers only that user's transports without extra args), and states the modifiable-only caveat. It does not explicitly contrast with GetTransport, so it lacks named alternatives/exclusions.

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