mcp-abap-adt

GetObjectsList

Recursively lists all child repository objects of ABAP programs, function groups, classes, packages, and composite objects, including nested includes and subcomponents, for one or multiple parents.

Instructions

[read-only] Recursively lists every child repository object of the program (PROG), function group (FUGR), class (CLAS), package (DEVC) or other composite object named by parent_name, parent_tech_name and parent_type, nested includes and subcomponents included. Takes parent_name, parent_tech_name and parent_type (one parent: its list) or objects (several parents: one entry per parent, in the order given, each { parent_name, parent_type, total_objects, objects } or { parent_name, parent_type, error }). Each level of the node tree is read in one ADT batch envelope. Runs on an ABAP session of its own. Optional timeout (seconds): when it passes, the read is cancelled, its ABAP session logged off, and the system stays as it was. Set it below your MCP client's request limit — the TypeScript SDK's client cancels at 60 s; a client's cancel ends only the client's wait, and SAP runs the read on. Runs outside batch mode.

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

Input Schema

Name	Required	Description
`objects`	No	[read-only] Several parents, read together (give this or parent_name)
`timeout`	No	Seconds to wait for the answer: a whole number, at least 1, no default — without it the call waits until SAP answers. When it passes, the read is cancelled (its ABAP session is logged off) and the call answers that nothing was changed. Set it below your MCP client's request limit — the TypeScript SDK's client cancels at 60 s; a cancel does nothing to SAP.
`parent_name`	No	[read-only] Parent object name (with parent_tech_name and parent_type; or give objects)
`parent_type`	No	[read-only] Parent object type (e.g. PROG/P, FUGR)
`parent_tech_name`	No	[read-only] Parent technical name
`with_short_descriptions`	No	[read-only] Include short descriptions (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv20.1.0Oct 24, 2026

addedInput schema / properties / objects

Added value: +{
+  "description": "[read-only] Several parents, read together (give this or parent_name)",
+  "items": {
+    "properties": {
+      "parent_name": {
+        "description": "Parent object name",
+        "type": "string"
+      },
+      "parent_type": {
+        "description": "Parent object type (e.g. PROG/P, FUGR)",
+        "type": "string"
+      }
+    },
+    "required": [
+      "parent_type",
+      "parent_name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / parent_name / description

Previous value: -"[read-only] Parent object name"New value: +"[read-only] Parent object name (with parent_tech_name and parent_type; or give objects)"

addedInput schema / properties / timeout

Added value: +{
+  "description": "Seconds to wait for the answer: a whole number, at least 1, no default — without it the call waits until SAP answers. When it passes, the read is cancelled (its ABAP session is logged off) and the call answers that nothing was changed. Set it below your MCP client's request limit — the TypeScript SDK's client cancels at 60 s; a cancel does nothing to SAP.",
+  "maximum": 2147483,
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / required

Removed value: -[
-  "parent_name",
-  "parent_tech_name",
-  "parent_type"
-]

First observedDec 29, 2025

TDQS

A4/5.0

Behavior5/5

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

With no structured annotations, the description carries the full behavioral burden and does so well: it declares read-only behavior, recursion into nested subcomponents, per-level ADT batch reads, a dedicated ABAP session, and timeout cancellation that logs off the session and leaves the system unchanged. It also warns that a client-side cancel does not stop SAP work.

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?

The purpose and read-only nature are front-loaded, and the content is dense but mostly justified for a complex recursive tool. Some timeout details are repeated verbatim in the schema and the description, but the description remains structured and readable.

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?

Given the complexity, schema richness, and absence of an output schema, the description is nearly complete. It explains recursion, batching, session behavior, timeout semantics, and multi-parent return shape; it is slightly incomplete on the exact return shape for the single-parent mode.

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 useful semantics beyond the schema: parent_name/parent_tech_name/parent_type represent one parent, objects represents several parents with preserved order, and the per-parent result shape is described including total_objects and error entries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it 'recursively lists every child repository object' of named composite parents, including nested includes. It is clear what the tool returns, but it never names or contrasts itself with close siblings such as GetObjectStructure or GetPackageContents.

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

Usage Guidelines3/5

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

It explains the two input modes (one parent using parent_name/parent_tech_name/parent_type, or several parents using objects), which implies usage. However, it gives no explicit guidance on when to choose this tool over similar repository-hierarchy tools, and no exclusions.

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

Deploy Server