ABAP-ADT-API MCP-Server

tracesHitList

Retrieve the hit list for a specific trace in ABAP systems to analyze execution events and performance data.

Instructions

Retrieves the hit list for a trace.

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": {
      "id": "<id>"
    },
    "name": "tracesHitList"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The ID of the trace.
`withSystemEvents`	No	Whether to include system events.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Mar 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states only that the tool 'retrieves' the hit list, implying a read operation, but does not reveal whether system events are included by default, any side effects, or the return format. This is a significant transparency 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?

The description is a single, concise sentence that communicates the core purpose without unnecessary words or repetition. It is appropriately sized for the tool's simplicity and is front-loaded with the key action.

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?

The description is too minimal for a tool with no output schema and no annotations. It does not explain what a 'hit list' contains, what the 'withSystemEvents' parameter means, or what the response looks like. Given the complexity of the surrounding tool set, this lack of context leaves the agent under-informed.

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?

The input schema fully describes both parameters (id and withSystemEvents) with 100% coverage. The description adds no additional meaning or context beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description clearly states the action ('Retrieves') and the resource ('the hit list for a trace'), providing a specific verb+resource combination. However, it does not explicitly differentiate from sibling tools like tracesList or tracesStatements, so it lacks sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not mention when to use this tool versus other trace-related tools, nor does it state prerequisites (such as requiring a valid trace ID) or exclusions. The schema implies an id is needed, but the description offers no contextual direction.

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

Deploy Server