mcp-abap-adt

RuntimeAnalyzeProfilerTrace

Reads an ABAP profiler trace view and returns a compact summary with totals and top entries so you can analyze runtime performance.

Instructions

[read-only] [runtime] Read profiler trace view and return compact analysis summary (totals + top entries). 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>"
    },
    "name": "RuntimeAnalyzeProfilerTrace"
  }
}

Input Schema

Name	Required	Description	Default
`top`	No	Number of top rows for summary. Default: 10.
`view`	No		hitlist
`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.
`trace_id_or_uri`	Yes	Profiler trace ID or full trace URI.
`with_system_events`	No	Include system events.

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

A3.8/5.0

Behavior5/5

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

With zero annotations the description carries the full burden and does so unusually well: it declares read-only, notes the call runs on its own ABAP session, explains that a timeout cancels the read and logs off that session leaving the system unchanged, and warns that a client-side cancel does not stop SAP. It also discloses the non-obvious batch-mode recording contract (empty content, answer read by number afterward).

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?

Core purpose is front-loaded and most sentences carry real operational information (session isolation, cancellation semantics, batch recording). It loses a little by repeating the timeout/MCP-client-limit material that already appears in the schema, and the long em-dash clauses make the middle sentences hard to scan.

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

Completeness3/5

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

Behavioral side effects are thoroughly covered, which is the hardest part. However, with no output schema the description should say more about the returned summary, and it leaves the three view modes unexplained, so an agent cannot judge what changing view actually yields.

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 coverage is 80%, so the schema already documents trace_id_or_uri, top, timeout and with_system_events. The description's timeout text largely restates the schema's own timeout description rather than adding new meaning, and it says nothing about the view enum values (hitlist/statements/db_accesses), which remain undocumented everywhere. Baseline 3.

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?

Opens with a specific verb and resource: "Read profiler trace view and return compact analysis summary (totals + top entries)." This clearly separates it from raw-data readers like RuntimeGetProfilerTraceData. It never names a sibling explicitly, so it stops short of a 5.

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?

Use is implied (you have a trace and want a summary), and the batch-mode paragraph tells you how calls behave in batch. But it never states when to pick this over RuntimeGetProfilerTraceData or RuntimeListProfilerTraceFiles, nor any prerequisite for obtaining a trace_id_or_uri.

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

Deploy Server