Skip to main content
Glama

GetInactiveObjects

Retrieve a list of modified but unactivated ABAP objects pending activation, including classes, tables, and CDS views, to manage activation tasks.

Instructions

[read-only] Get a list of inactive ABAP objects — modified but not yet activated, pending activation. Shows classes, tables, CDS views, and other objects awaiting activation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function that retrieves inactive ABAP objects via ADT client and returns them as JSON.
    export async function handleGetInactiveObjects(
      context: HandlerContext,
      _params: any,
    ) {
      const { connection, logger } = context;
      try {
        const client = createAdtClient(connection, logger);
        const utils = client.getUtils();
    
        logger?.info('Retrieving inactive objects...');
        const result = await utils.getInactiveObjects();
    
        return return_response({
          data: JSON.stringify(
            {
              success: true,
              count: result.objects.length,
              objects: result.objects,
            },
            null,
            2,
          ),
          status: 200,
          statusText: 'OK',
          headers: {},
          config: {} as any,
        });
      } catch (error: any) {
        logger?.error('Error retrieving inactive objects:', error);
        return return_error(error);
      }
    }
  • Tool definition with name 'GetInactiveObjects', description, and empty input schema (no parameters required).
    export const TOOL_DEFINITION = {
      name: 'GetInactiveObjects',
      available_in: ['onprem', 'cloud'] as const,
      description:
        '[read-only] Get a list of inactive ABAP objects — modified but not yet activated, pending activation. Shows classes, tables, CDS views, and other objects awaiting activation.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    } as const;
  • Registration of GetInactiveObjects tool in SystemHandlersGroup with its tool definition and handler binding.
    {
      toolDefinition: GetInactiveObjects_Tool,
      handler: (args: any) => handleGetInactiveObjects(this.context, args),
  • Import of the GetInactiveObjects tool definition and handler into SystemHandlersGroup.
    import {
      TOOL_DEFINITION as GetInactiveObjects_Tool,
      handleGetInactiveObjects,
    } from '../../../handlers/system/readonly/handleGetInactiveObjects';
Behavior3/5

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

With no annotations, the description adds value by marking the tool as read-only and explaining the result set. However, it omits details like whether results are paginated or if there are performance implications.

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?

Two concise sentences with the critical read-only hint front-loaded. Every word adds value.

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 no parameters or output schema, the description adequately covers the tool's purpose and result. It could mention that no filtering is possible, but is reasonably complete.

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?

No parameters exist, and schema coverage is 100%. Per guidelines, baseline is 4.

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 clearly states the tool retrieves a list of inactive ABAP objects (modified but not activated), specifying the types of objects included. It distinguishes well from siblings like Activate* and Get* tools.

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?

No explicit guidance on when to use this tool versus alternatives. The context of many sibling Get* tools implies a query for inactive objects, but it does not clarify when to prefer this over GetClass, GetTable, etc.

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