Skip to main content
Glama

RuntimeListProfilerTraceFiles

List ABAP profiler trace files available in ADT runtime and get parsed JSON payload.

Instructions

[runtime] List ABAP profiler trace files available in ADT runtime. Returns parsed JSON payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for RuntimeListProfilerTraceFiles. It uses AdtRuntimeClient to get profiler trace files from ADT runtime and returns the parsed JSON payload.
    export async function handleRuntimeListProfilerTraceFiles(
      context: HandlerContext,
    ) {
      const { connection, logger } = context;
    
      try {
        const runtimeClient = new AdtRuntimeClient(connection, logger);
        const response = await runtimeClient.getProfiler().list();
    
        return return_response({
          data: JSON.stringify(
            {
              success: true,
              status: response.status,
              payload: parseRuntimePayloadToJson(response.data),
            },
            null,
            2,
          ),
          status: response.status,
          statusText: response.statusText,
          headers: response.headers,
          config: response.config,
        });
      } catch (error: any) {
        logger?.error('Error listing profiler trace files:', error);
        return return_error(error);
      }
    }
  • Tool definition including name, description, availability (onprem/cloud), and input schema (no required inputs).
    export const TOOL_DEFINITION = {
      name: 'RuntimeListProfilerTraceFiles',
      available_in: ['onprem', 'cloud'] as const,
      description:
        '[runtime] List ABAP profiler trace files available in ADT runtime. Returns parsed JSON payload.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    } as const;
  • Import of the handler and tool definition from the handler file.
    import {
      handleRuntimeListProfilerTraceFiles,
      TOOL_DEFINITION as RuntimeListProfilerTraceFiles_Tool,
    } from '../../../handlers/system/readonly/handleRuntimeListProfilerTraceFiles';
  • Registration of RuntimeListProfilerTraceFiles tool in the SystemHandlersGroup with its tool definition and handler.
    {
      toolDefinition: RuntimeListProfilerTraceFiles_Tool,
      handler: () => handleRuntimeListProfilerTraceFiles(this.context),
    },
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'returns parsed JSON payload' but does not confirm it as a read-only operation, specify required permissions, describe pagination or filtering behavior, or indicate any side effects. For a list tool, anonymity about safety is a gap.

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 brief, front-loaded sentences with no redundant information. Each sentence adds distinct value: the first states the function, the second clarifies the output format.

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?

For a zero-parameter, no-output-schema list tool, the description provides essential purpose and return type. However, it lacks details like the structure of the JSON payload, any ordering, limits, or preconditions (e.g., profiling must be active). This is adequate but not exhaustive.

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?

The input schema has zero parameters, so the description’s note that it lists 'all ABAP profiler trace files' adds necessary context about the implicit lack of filtering. Schema coverage is 100% trivially, and the description adds no further parameter details, but none are needed.

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 action (list), the resource (ABAP profiler trace files), the context (ADT runtime), and the output format (parsed JSON payload). It effectively distinguishes this tool from related runtime profiler siblings like RuntimeAnalyzeProfilerTrace and RuntimeGetProfilerTraceData.

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 implicitly suggests this tool is used to enumerate available trace files, but it does not explicitly state when to prefer it over alternatives, nor does it provide any exclusions or prerequisites. The sibling tools include other profiler-related operations, which could confuse an agent without clearer guidance.

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