Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetVirtualFoldersLow

Browses ABAP objects by retrieving hierarchical virtual folder contents from the ADT information system, filtered by package, group, or type.

Instructions

[low-level] Retrieve hierarchical virtual folder contents from ADT information system. Used for browsing ABAP objects by package, group, type, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
facet_orderNoOrder of facets in response (e.g., ["package", "group", "type"]). Default: ["package", "group", "type"]
preselectionNoOptional preselection filters (facet-value pairs for filtering)
with_versionsNoInclude version information in response
object_search_patternNoObject search pattern: "*" matches any name, and a trailing "*" matches a prefix. Default: "*"*
ignore_short_descriptionsNoIgnore short descriptions in response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / object_search_pattern / description
      Previous value: -"Object search pattern (e.g., \"*\", \"Z*\", \"ZCL_*\"). Default: \"*\""New value: +"Object search pattern: \"*\" matches any name, and a trailing \"*\" matches a prefix. Default: \"*\""
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies a read operation, but it does not disclose the result shape, pagination/volume behavior, the effect of the '[low-level]' marker, or whether the operation is safe and side-effect free. For a 6-parameter discovery tool this is thin.

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?

Two sentences, no padding, with the '[low-level]' qualifier and the core verb front-loaded. It is appropriately sized, though the second sentence is doing only light work and neither sentence arrives at the specifics (facets, filtering) the tool actually exposes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters, no output schema, and no annotations, the description is only barely sufficient: it names the domain and the browsing intent but omits the virtual-folder/facet model, the meaning of the detail levels, and how it differs from sibling tree tooling. Adequate to start, incomplete for reliable selection.

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 explains detail, facet_order, preselection, object_search_pattern, and the rest; the baseline of 3 applies. The description adds no parameter semantics of its own (e.g., no guidance on when to use 'full' vs 'raw' or how preselection interacts with facet_order).

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?

States a specific verb+resource combo ('Retrieve hierarchical virtual folder contents') and adds the domain ('from ADT information system') plus an example use ('browsing ABAP objects by package, group, type'). However it does not distinguish itself from close siblings such as GetPackageTree, GetNodeStructureLow, or GetObjectStructureLow, so an agent cannot route between the 'Low' variants on the description alone.

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?

'Used for browsing ABAP objects by package, group, type, etc.' implies the usage context, but there is no explicit when-to-use vs. when-not, no mention of when the non-low GetVirtualFolders variant or alternate tree tools should be picked, and no prerequisites. Usage is inferable but not navigational.

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