Skip to main content
Glama

Sap Se09 Lookup

sap_se09_lookup
Read-only

Look up SAP transport requests from SE09 Transport Organizer, including owner, status, type, and target system, and filter by user, request type, or status for ECC release workflows.

Instructions

Look up transport requests from SE09 (Transport Organizer). If sap-adt is available, prefer its get_transport_requests for listing transports. USE THIS for transport release on ECC (ADT release silently fails on ECC) or when ADT is unavailable. Returns transport requests with owner, description, status, type, and target system. By default shows only modifiable requests for the current user. Supports filtering by username, request type (workbench/customizing), and status (modifiable/released/all).

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": "sap_se09_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status - "modifiable", "released", or "all" (default: "modifiable")modifiable
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
usernameNoFilter by owner (default: current SAP user)
output_fileNoIf provided, write results to this JSON file within the configured output directory (OUTPUT_DIR, default: current working directory) (on success only).
request_typeNoFilter by type - "workbench", "customizing", or "all"all
include_objectsNoIf True, expand the tree to include tasks under each request. This is slower (~2s per transport) but provides task details.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
requestsNoTransport requests found
retrieved_atYesWhen the data was retrieved
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
request_countNoNumber of requests returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is partly covered. The description still adds real value by disclosing the default scoping (only modifiable requests for the current user), the returned fields, and a compatibility caveat about ADT failing on ECC. What it does not clarify is the ambiguity of "USE THIS for transport release," which reads as if the tool performs a release rather than only looking transports up for one.

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?

Five sentences, each carrying routing, scoping, or return-shape information, with the most decision-relevant point (prefer ADT, use this on ECC) front-loaded. The return-field enumeration is somewhat redundant given an output schema exists, which is the only wasted space.

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 seven-parameter, zero-required lookup with full schema coverage, annotations, and an output schema, the description covers routing, defaults, and filtering well enough to call it correctly. The one residual gap is the unclear phrasing around transport release, which could lead an agent to expect the tool to perform a release action.

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 every parameter including status, request_type, username, include_objects and output_file is already documented with enums and defaults. The description restates the same filtering dimensions (username, workbench/customizing, modifiable/released/all) plus the current-user default, adding confirmation but no new syntax or edge-case meaning, so the 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 ("Look up transport requests from SE09 (Transport Organizer)") and immediately names the competing mechanism (sap-adt's get_transport_requests). An agent can distinguish this from the many other sap_*_lookup siblings because it identifies the exact SAP transaction (SE09) and the object type (transports) it covers.

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?

Explicit routing rules: prefer ADT's get_transport_requests when sap-adt is available, use this one when ADT is unavailable, and use this for release workflows on ECC because ADT release silently fails there. That is a clear when-to-use, when-not-to-use, and named alternative in a single passage.

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