mcp-abap-adt

RuntimeGetProfilerTraceData

Reads ABAP profiler trace data by trace ID or URI for hitlist, statements, or database access views, returning parsed JSON with optional timeout and detail controls.

Instructions

[read-only] [runtime] Read profiler trace data by trace id/uri: hitlist, statements, or db accesses. Returns parsed JSON payload. Runs on an ABAP session of its own. Optional timeout (seconds): when it passes, the read is cancelled, its ABAP session logged off, and the system stays as it was. Set it below your MCP client's request limit — the TypeScript SDK's client cancels at 60 s; a client's cancel ends only the client's wait, and SAP runs the read on. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trace_id_or_uri": "<trace_id_or_uri>",
      "view": "<view>"
    },
    "name": "RuntimeGetProfilerTraceData"
  }
}

Input Schema

Name	Required	Description
`id`	No	Statement node ID (for statements view).
`view`	Yes	Trace view to retrieve.
`timeout`	No	Seconds to wait for the answer: a whole number, at least 1, no default — without it the call waits until SAP answers. When it passes, the read is cancelled (its ABAP session is logged off) and the call answers that nothing was changed. Set it below your MCP client's request limit — the TypeScript SDK's client cancels at 60 s; a cancel does nothing to SAP.
`with_details`	No	Include statement details (for statements view).
`trace_id_or_uri`	Yes	Profiler trace ID or full ADT trace URI.
`with_system_events`	No	Include system events.
`auto_drill_down_threshold`	No	Auto drill-down threshold (for statements view).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv20.1.0Oct 24, 2026

addedInput schema / properties / timeout

Added value: +{
+  "description": "Seconds to wait for the answer: a whole number, at least 1, no default — without it the call waits until SAP answers. When it passes, the read is cancelled (its ABAP session is logged off) and the call answers that nothing was changed. Set it below your MCP client's request limit — the TypeScript SDK's client cancels at 60 s; a cancel does nothing to SAP.",
+  "maximum": 2147483,
+  "minimum": 1,
+  "type": "integer"
+}

AddedMar 14, 2026

TDQS

A4/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it declares read-only behavior, discloses that the read runs on a dedicated ABAP session, that a timeout cancels the read and logs off that session leaving the system unchanged, that a client-side cancel does not stop SAP, and that in batch mode the call returns empty content recorded under a sequence number.

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?

Front-loaded with purpose and views before the operational caveats, and every sentence carries real information. The timeout paragraph is somewhat long and partially duplicates the schema's timeout description, keeping it from a 5.

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

Completeness5/5

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

There is no output schema, yet the description states the return is a parsed JSON payload and warns that in batch mode the immediate answer is empty content retrieved later by number. Combined with the side-effect and session behavior disclosure, an agent has everything needed to call it safely and interpret the result.

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 description coverage is 100%, so the schema already documents all seven parameters, including the timeout semantics restated almost verbatim in the description. The description adds no syntax or example values beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (read profiler trace data) plus the three enumerable views (hitlist, statements, db accesses), which lets an agent map directly to the schema enum. It does not, however, distinguish itself from sibling RuntimeAnalyzeProfilerTrace, which an agent could plausibly confuse it with.

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 gives operational guidance (own ABAP session, timeout recommended below the client's 60 s limit, batch-mode recording) but never says when to choose this over RuntimeAnalyzeProfilerTrace or RuntimeListProfilerTraceFiles, nor when to pick a given view. Usage is implied by the view names rather than stated.

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

Deploy Server