Skip to main content
Glama

RuntimeListProfilerTraceFiles

Lists ABAP profiler trace files in ADT runtime so you can identify recordings by user, object, state, and expiration before analyzing them.

Instructions

[read-only] [runtime] List ABAP profiler trace files available in ADT runtime. Returns structured entries with id, recordedAt, user, objectName, state, expiresAt, and sizing/timing fields. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "RuntimeListProfilerTraceFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it declares the operation as read-only, enumerates the returned entry fields, and explains unusual batch-mode recording behavior where calls return empty content and answers are read by number later. It omits permission requirements and any pagination or size limits.

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 front-loaded with the core listing purpose and uses compact bracketed tags. The batch-mode sentence is dense and slightly convoluted, but it contains important operational information rather than filler.

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, read-only listing tool with no output schema, the description supplies a useful field list and batch-mode behavior. It could say more about state or expiry semantics and whether results are paginated, but it is largely complete for correct invocation.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, though it does describe the returned entry fields instead.

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 uses a specific verb and resource: "List ABAP profiler trace files available in ADT runtime." It clearly distinguishes this listing operation from sibling runtime tools such as RuntimeGetProfilerTraceData and RuntimeCreateProfilerTraceParameters.

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?

Usage is implied by the listing purpose, and the batch-mode note provides some operational context. However, it never explicitly states when to use this tool instead of RuntimeGetProfilerTraceData, RuntimeAnalyzeProfilerTrace, or RuntimeCreateProfilerTraceParameters.

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