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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Transport Info for Object

get_transport_for_object
Read-onlyIdempotent

Reports an ABAP object's transport details—package, recording need, existing lock, and available open requests—so you can choose the right transport before writing or deleting source.

Instructions

Report how a change to an ABAP object is transported: its package, whether recording is needed (a local $ package needs none), the request it is already locked into, and the open requests the transport layer allows. Use it before write_abap_object_source or delete_abap_object to pick a transport; list_all_transports shows open requests generally. Read-only; takes no lock and creates no request.

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": {
      "url": "<url>"
    },
    "name": "get_transport_for_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesADT URL of the object (e.g. /sap/bc/adt/programs/programs/ZREPORT)
packageNameNoPackage of the object (e.g. ZORDER_API); optional, passed to ADT together with the URL
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.2
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name of the object"New value: +"Package of the object (e.g. ZORDER_API); optional, passed to ADT together with the URL"
    • changedInput schema / properties / url / description
      Previous value: -"ADT URL of the object"New value: +"ADT URL of the object (e.g. /sap/bc/adt/programs/programs/ZREPORT)"
  2. First observedv1.16.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description still adds real value by stating it takes no lock and creates no request, and by giving the domain rule that a local $ package requires no recording. It stops short of describing error behavior or return shape.

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 short sentences, front-loaded with the return payload before the usage routing and the behavioral caveat. Every clause carries information: what it reports, when to call it, what it does not do.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it does so at the field level (package, recording flag, locked request, allowed requests). It could be slightly richer about the exact response structure, but nothing needed to select or invoke the tool is missing.

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 url, packageName and connectionId are already documented with examples; the description adds no syntax or format detail beyond that. The only adjacent hint is the local $ package note, which indirectly bears on packageName, 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?

The description leads with a specific verb and resource ("Report how a change to an ABAP object is transported") and enumerates exactly what is returned: package, recording requirement, current lock request, and allowed open requests. It is immediately distinguishable from list_all_transports, which it names as the general-purpose alternative.

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?

It states precisely when to call it ("before write_abap_object_source or delete_abap_object to pick a transport") and names the alternative for the broader case ("list_all_transports shows open requests generally"). No inference is required to choose between the two.

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