Skip to main content
Glama

GetVirtualFoldersLow

Browse ABAP objects by package, group, or type using hierarchical virtual folders. Retrieve organized folder contents from the ADT information system with optional filters for object search pattern and facet ordering.

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
object_search_patternNoObject search pattern (e.g., "*", "Z*", "ZCL_*"). Default: "*"*
preselectionNoOptional preselection filters (facet-value pairs for filtering)
facet_orderNoOrder of facets in response (e.g., ["package", "group", "type"]). Default: ["package", "group", "type"]
with_versionsNoInclude version information in response
ignore_short_descriptionsNoIgnore short descriptions in response

Implementation Reference

  • Main handler function for GetVirtualFoldersLow MCP tool. Uses AdtUtils getVirtualFoldersContents to retrieve hierarchical virtual folder contents.
    export async function handleGetVirtualFolders(
      context: HandlerContext,
      args: GetVirtualFoldersArgs,
    ) {
      const { connection, logger } = context;
      try {
        // Create AdtClient and get utilities
        const client = createAdtClient(connection, logger);
        const utils = client.getUtils();
    
        logger?.info('Fetching virtual folders contents');
    
        const params = {
          objectSearchPattern: args.object_search_pattern || '*',
          preselection: args.preselection,
          facetOrder: args.facet_order || ['package', 'group', 'type'],
          withVersions: args.with_versions,
          ignoreShortDescriptions: args.ignore_short_descriptions,
        };
    
        const result = await utils.getVirtualFoldersContents(params);
    
        logger?.debug('Virtual folders contents fetched successfully');
    
        return return_response(result);
      } catch (error: any) {
        logger?.error('Failed to fetch virtual folders contents', error);
        return return_error(error);
      }
    }
  • Tool definition including name 'GetVirtualFoldersLow', available_in, description, and inputSchema with properties: object_search_pattern, preselection, facet_order, with_versions, ignore_short_descriptions.
    export const TOOL_DEFINITION = {
      name: 'GetVirtualFoldersLow',
      available_in: ['onprem', 'cloud'] as const,
      description:
        '[low-level] Retrieve hierarchical virtual folder contents from ADT information system. Used for browsing ABAP objects by package, group, type, etc.',
      inputSchema: {
        type: 'object',
        properties: {
          object_search_pattern: {
            type: 'string',
            description:
              'Object search pattern (e.g., "*", "Z*", "ZCL_*"). Default: "*"',
            default: '*',
          },
          preselection: {
            type: 'array',
            description:
              'Optional preselection filters (facet-value pairs for filtering)',
            items: {
              type: 'object',
              properties: {
                facet: {
                  type: 'string',
                  description: 'Facet name (e.g., "package", "group", "type")',
                },
                values: {
                  type: 'array',
                  items: { type: 'string' },
                  description: 'Array of facet values to filter by',
                },
              },
              required: ['facet', 'values'],
            },
          },
          facet_order: {
            type: 'array',
            items: { type: 'string' },
            description:
              'Order of facets in response (e.g., ["package", "group", "type"]). Default: ["package", "group", "type"]',
            default: ['package', 'group', 'type'],
          },
          with_versions: {
            type: 'boolean',
            description: 'Include version information in response',
            default: false,
          },
          ignore_short_descriptions: {
            type: 'boolean',
            description: 'Ignore short descriptions in response',
            default: false,
          },
        },
        required: [],
      },
    } as const;
  • Registration of GetVirtualFoldersLow tool in SystemHandlersGroup.getHandlers() - maps toolDefinition and handler.
    {
      toolDefinition: GetVirtualFoldersLow_Tool,
      handler: (args: any) => {
        return handleGetVirtualFolders(this.context, args);
      },
  • Import of TOOL_DEFINITION as GetVirtualFoldersLow_Tool from the handler file.
      TOOL_DEFINITION as GetVirtualFoldersLow_Tool,
      handleGetVirtualFolders,
    } from '../../../handlers/system/low/handleGetVirtualFolders';
Behavior2/5

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

No annotations are provided, so the description carries full burden. It indicates the tool is 'low-level' and 'retrieve' but does not disclose behavioral traits such as read-only nature, permissions required, performance implications, or response structure. The absence of output schema exacerbates the gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but the inclusion of '[low-level]' is somewhat meta. It is front-loaded but lacks structured detail. It could benefit from expansion.

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

Completeness2/5

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

Given the lack of output schema and the complexity of hierarchical browsing, the description is incomplete. It does not describe the response format or hierarchy, and does not differentiate from similar sibling tools. Significant gaps remain.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions, which already explain the parameters adequately.

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 clearly states the tool retrieves hierarchical virtual folder contents from the ADT information system, with a specific verb 'retrieve' and resource. It mentions browsing ABAP objects by package, group, type, which adds context but does not explicitly differentiate from siblings like GetNodeStructureLow 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?

The description implies usage for browsing ABAP objects by package, group, type, but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. No exclusions or alternative tools are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fr0ster/mcp-abap-adt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server