Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

delete_trace_config

Delete a trace configuration by specifying its unique ID and optionally a system ID, to remove outdated or unnecessary trace collection settings.

Instructions

Delete a trace collection configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
config_idYesConfiguration ID to delete
system_idNoSAP system ID (e.g. DEV). Omit to use default system.

Implementation Reference

  • Tool registration in the ListToolsRequestSchema handler — defines the 'delete_trace_config' tool name, description, and input schema (requires config_id string and optional system_id).
    {
      name: "delete_trace_config",
      description: "Delete a trace collection configuration",
      inputSchema: {
        type: "object" as const,
        properties: {
          config_id: { type: "string", description: "Configuration ID to delete" },
          ...SYSTEM_ID_PROP,
        },
        required: ["config_id"],
      },
    },
  • Input validation schema for delete_trace_config — validates the 'config_id' field as a required string.
    const TraceConfigIdSchema = z.object({ config_id: z.string() });
  • Handler in the CallToolRequestSchema switch — parses input with TraceConfigIdSchema, calls client.deleteTraceConfig(), and returns the result as text.
    case "delete_trace_config": {
      const { config_id } = TraceConfigIdSchema.parse(args);
      const result = await client.deleteTraceConfig(config_id);
      return { content: [{ type: "text", text: result }] };
    }
  • Helper method on AdtClient — performs an HTTP DELETE to the ADT trace config endpoint using CSRF token, returning the response or a default success message.
    async deleteTraceConfig(configId: string): Promise<string> {
      const resp = await this.deleteWithCsrf(
        `/sap/bc/adt/runtime/traces/abaptraces/requests/${encodeURIComponent(configId)}`
      );
      return resp.data as string || "Trace configuration deleted";
    }
Behavior2/5

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

With no annotations, the description fully bears the burden of disclosing behaviors, but it only states 'Delete' without explaining side effects, reversibility, or permissions. The agent has no insight into the consequences of invoking this tool.

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?

The description is concise at only five words, which is efficient for a simple delete operation. However, given the lack of annotations, a slightly more detailed description could have been warranted.

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 destructive action with no output schema and no annotations, the description is insufficiently complete. It omits critical behavioral context such as confirmation requirements, effects on related data, or error conditions.

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 already documents both parameters with 100% coverage. The description adds no additional semantic information beyond what the schema provides, so it meets the baseline but does not improve clarity.

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 verb 'Delete' and the resource 'trace collection configuration', making the purpose straightforward. However, it does not differentiate from the sibling tool 'delete_trace', which may cause confusion about which resource is being deleted.

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 guidance is provided on when to use this tool instead of alternatives like 'delete_trace' or 'create_trace_config'. The description lacks context for selection.

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