mcp-abap-adt

RuntimeCreateProfilerTraceParameters

Schedules ABAP profiler trace parameters and returns a profiler ID for profiled execution, enabling targeted runtime analysis in SAP systems.

Instructions

[read-only] [runtime] Schedule ABAP profiler trace parameters and return profilerId (the request id) for profiled execution. 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": {
      "description": "<description>"
    },
    "name": "RuntimeCreateProfilerTraceParameters"
  }
}

Input Schema

Name	Required	Description
`aggregate`	No
`sql_trace`	No
`amdp_trace`	No
`description`	Yes	Human-readable trace description.
`all_db_events`	No
`explicit_on_off`	No
`with_rfc_tracing`	No
`all_dynpro_events`	No
`all_procedural_units`	No
`max_time_for_tracing`	No
`max_size_for_trace_file`	No
`all_misc_abap_statements`	No
`all_system_kernel_events`	No
`all_internal_table_events`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedMar 14, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two non-obvious traits: the self-declared read-only nature and the batch-mode behavior (recorded under the next number, empty answer, read later by number), which is genuinely useful. It omits whether a trace is actually started or left armed, permission requirements, and any defaults for the 14 flags.

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?

Two dense sentences with the core action and return value front-loaded, followed by the batch caveat. Terse but no wasted clauses, given the specialized SAP terminology.

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?

For a 14-parameter, 7%-coverage tool with no output schema, the description covers only the return value and batch semantics. An agent still cannot tell what most of the trace configuration flags do or how to reasonably populate them.

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

Parameters2/5

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

Schema description coverage is only 7% and the description explains none of the 13 undocumented flags (aggregate, sql_trace, amdp_trace, all_db_events, explicit_on_off, max_time_for_tracing, etc.). Only the required 'description' parameter is self-documenting in the schema, so the description leaves most parameter semantics unexplained.

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: schedule ABAP profiler trace parameters and return a profilerId for profiled execution. This is distinguishable from siblings like RuntimeListProfilerTraceFiles, RuntimeGetProfilerTraceData, and RuntimeAnalyzeProfilerTrace, though it never explicitly names which sibling it pairs 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 batch-mode sentence implies a usage context (call it inside a batch, read the answer by number after BatchEnd), which implicitly points at the batch siblings. There is no explicit guidance on when to choose this versus RuntimeRunClass/RuntimeRunProgram or how the returned profilerId is subsequently consumed.

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

Deploy Server