Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

list_traces

List ABAP runtime traces (SAT/SE30) for a given SAP user. Traces must be pre-recorded via SAP GUI. Optionally specify system ID.

Instructions

List ABAP runtime traces (SAT/SE30) for a user. Traces must be created via SAP GUI (transaction SAT or SE30) since the ADT REST API cannot profile programrun executions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoSAP username (default: current user)
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Tool registration in ListToolsRequestSchema handler — defines tool name, description, and input schema for list_traces
    {
      name: "list_traces",
      description: "List ABAP runtime traces (SAT/SE30) for a user. Traces must be created via SAP GUI (transaction SAT or SE30) since the ADT REST API cannot profile programrun executions.",
      inputSchema: {
        type: "object" as const,
        properties: {
          user: { type: "string", description: "SAP username (default: current user)" },
          ...SYSTEM_ID_PROP,
        },
        required: [],
      },
    },
  • Zod schema definition for list_traces input — accepts optional 'user' string
    const TraceUserSchema = z.object({ user: z.string().optional() });
  • Handler in CallToolRequestSchema — parses args with TraceUserSchema, delegates to AdtClient.listTraces(user)
    case "list_traces": {
      const { user } = TraceUserSchema.parse(args);
      const result = await client.listTraces(user);
      return { content: [{ type: "text", text: result }] };
    }
  • Helper method on AdtClient — makes GET request to SAP ADT REST API to list ABAP runtime traces for a user
    async listTraces(user?: string): Promise<string> {
      const u = encodeURIComponent((user ?? this.config.username).toUpperCase());
      const response = await this.http.get<string>(
        `/sap/bc/adt/runtime/traces/abaptraces?user=${u}`,
        { headers: { Accept: "*/*" }, responseType: "text" }
      );
      return response.data;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a key limitation (cannot create traces via API) but does not describe output behavior, pagination, or filtering details.

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?

Two sentences with no redundant information, front-loaded with the core purpose. Every sentence adds value.

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 simple list tool with two parameters and no output schema, the description covers purpose and a key constraint. It lacks details about output format but is adequate for the tool's simplicity.

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 100% and already includes descriptions (user defaults to current user, system_id example DEV). The description adds no additional semantic value beyond the schema.

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 clearly states the tool lists ABAP runtime traces (SAT/SE30) for a user, specifying the verb and resource. It distinguishes itself from siblings like delete_trace or create_trace_config by focusing on listing.

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

Usage Guidelines4/5

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

The description explains that traces must be created via SAP GUI, not with this tool, providing clear when-not-to-use guidance. However, it does not explicitly mention alternative tools or scenarios for using this tool over others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ethanhan2014/sap-adt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server