Skip to main content
Glama

RuntimeCreateProfilerTraceParameters

Creates ABAP profiler trace parameters with user-defined settings and returns a profilerId to initiate profiled execution for performance analysis.

Instructions

[runtime] Create ABAP profiler trace parameters and return profilerId (URI) for profiled execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesHuman-readable trace description.
all_misc_abap_statementsNo
all_procedural_unitsNo
all_internal_table_eventsNo
all_dynpro_eventsNo
aggregateNo
explicit_on_offNo
with_rfc_tracingNo
all_system_kernel_eventsNo
sql_traceNo
all_db_eventsNo
max_size_for_trace_fileNo
amdp_traceNo
max_time_for_tracingNo

Implementation Reference

  • Main handler function that creates ABAP profiler trace parameters. Uses AdtRuntimeClient to get the profiler, calls createParameters with the provided args, extracts the profilerId from the response, and returns success data with the profiler_id.
    export async function handleRuntimeCreateProfilerTraceParameters(
      context: HandlerContext,
      args: RuntimeCreateProfilerTraceParametersArgs,
    ) {
      const { connection, logger } = context;
    
      try {
        if (!args?.description) {
          throw new Error('Parameter "description" is required');
        }
    
        const runtimeClient = new AdtRuntimeClient(connection, logger);
        const profiler = runtimeClient.getProfiler();
        const response = await profiler.createParameters({
          description: args.description,
          allMiscAbapStatements: args.all_misc_abap_statements,
          allProceduralUnits: args.all_procedural_units,
          allInternalTableEvents: args.all_internal_table_events,
          allDynproEvents: args.all_dynpro_events,
          aggregate: args.aggregate,
          explicitOnOff: args.explicit_on_off,
          withRfcTracing: args.with_rfc_tracing,
          allSystemKernelEvents: args.all_system_kernel_events,
          sqlTrace: args.sql_trace,
          allDbEvents: args.all_db_events,
          maxSizeForTraceFile: args.max_size_for_trace_file,
          amdpTrace: args.amdp_trace,
          maxTimeForTracing: args.max_time_for_tracing,
        });
    
        const profilerId = (profiler as Profiler).extractIdFromResponse(response);
    
        return return_response({
          data: JSON.stringify(
            {
              success: true,
              profiler_id: profilerId,
              status: response.status,
            },
            null,
            2,
          ),
          status: response.status,
          statusText: response.statusText,
          headers: response.headers,
          config: response.config,
        });
      } catch (error: any) {
        logger?.error('Error creating profiler trace parameters:', error);
        return return_error(error);
      }
    }
  • TOOL_DEFINITION constant defining the tool's name ('RuntimeCreateProfilerTraceParameters'), availability ('onprem', 'cloud'), description, and inputSchema with properties like description (required), various boolean trace flags, and numeric size/time limits.
    export const TOOL_DEFINITION = {
      name: 'RuntimeCreateProfilerTraceParameters',
      available_in: ['onprem', 'cloud'] as const,
      description:
        '[runtime] Create ABAP profiler trace parameters and return profilerId (URI) for profiled execution.',
      inputSchema: {
        type: 'object',
        properties: {
          description: {
            type: 'string',
            description: 'Human-readable trace description.',
          },
          all_misc_abap_statements: { type: 'boolean' },
          all_procedural_units: { type: 'boolean' },
          all_internal_table_events: { type: 'boolean' },
          all_dynpro_events: { type: 'boolean' },
          aggregate: { type: 'boolean' },
          explicit_on_off: { type: 'boolean' },
          with_rfc_tracing: { type: 'boolean' },
          all_system_kernel_events: { type: 'boolean' },
          sql_trace: { type: 'boolean' },
          all_db_events: { type: 'boolean' },
          max_size_for_trace_file: { type: 'number' },
          amdp_trace: { type: 'boolean' },
          max_time_for_tracing: { type: 'number' },
        },
        required: ['description'],
      },
    } as const;
  • TypeScript interface defining the strongly-typed args for the handler, mapping the snake_case input schema properties to their expected types.
    interface RuntimeCreateProfilerTraceParametersArgs {
      description: string;
      all_misc_abap_statements?: boolean;
      all_procedural_units?: boolean;
      all_internal_table_events?: boolean;
      all_dynpro_events?: boolean;
      aggregate?: boolean;
      explicit_on_off?: boolean;
      with_rfc_tracing?: boolean;
      all_system_kernel_events?: boolean;
      sql_trace?: boolean;
      all_db_events?: boolean;
      max_size_for_trace_file?: number;
      amdp_trace?: boolean;
      max_time_for_tracing?: number;
    }
  • Registration of the tool in SystemHandlersGroup.getHandlers(). Uses RuntimeCreateProfilerTraceParameters_Tool as the toolDefinition and wires it to handleRuntimeCreateProfilerTraceParameters.
    {
      toolDefinition: RuntimeCreateProfilerTraceParameters_Tool,
      handler: (args: any) =>
        handleRuntimeCreateProfilerTraceParameters(this.context, args),
    },
  • Import of the handler function and TOOL_DEFINITION (aliased as RuntimeCreateProfilerTraceParameters_Tool) from the handler file.
    import {
      handleRuntimeCreateProfilerTraceParameters,
      TOOL_DEFINITION as RuntimeCreateProfilerTraceParameters_Tool,
    } from '../../../handlers/system/readonly/handleRuntimeCreateProfilerTraceParameters';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states creation and return of an ID, but omits details such as mutation effects, authorization requirements, side effects, or what happens if parameters are invalid. The description is insufficient for safe or informed invocation.

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 description is a single sentence that efficiently conveys the core action and outcome. It is appropriately sized for a simple creation tool, though a bit more structure (e.g., noting key parameters or prerequisites) could enhance clarity without losing conciseness.

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 tool's complexity (14 parameters, no output schema, no annotations), the description is incomplete. It fails to explain parameter roles, return value format, or how the profilerId is used. Agents lack sufficient context to correctly select and invoke this tool without external knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 7% (only 'description' has a description). The tool description does not add meaning to any of the 14 parameters, leaving 13 boolean or numeric parameters unexplained. Agents have no semantic understanding of parameters like 'all_misc_abap_statements' or 'aggregate'.

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 creates ABAP profiler trace parameters and returns a profilerId as URI. It uses a specific verb ('Create') and resource ('ABAP profiler trace parameters'), and the distinct result distinguishes it from sibling tools like RuntimeRunClassWithProfiling or RuntimeAnalyzeProfilerTrace.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this tool is a prerequisite for profiling runs or compare it to other profiling tools like RuntimeRunClassWithProfiling. The lack of usage context reduces agent decision support.

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