mcp-abap-abap-adt-api

tracesDeleteConfiguration

Destructive

Delete a trace configuration to stop further recording of trace data under it.

Instructions

Delete a trace configuration, so nothing more is recorded under it.

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": "tracesDeleteConfiguration"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The ID of the trace configuration.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the agent knows this is destructive. The description adds 'so nothing more is recorded under it,' which clarifies the consequence beyond the mere destructive flag. This provides useful behavioral context that annotations alone do not convey.

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 front-loads the action ('Delete') and the object ('trace configuration'), with no extraneous words. Every element contributes to understanding the tool's purpose.

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

Completeness5/5

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

For a simple delete operation with one parameter, the description fully covers what the tool does and its effect (stops recording). The destructive annotation covers safety, and no output schema is expected. Nothing an agent needs to call it correctly is missing.

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 schema provides 100% coverage for the single 'id' parameter with a description. The tool description adds no additional semantics about the parameter (e.g., format, ownership, or validation). Baseline 3 is appropriate since the schema carries the full burden.

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 verb 'Delete' and the resource 'trace configuration', and adds the purpose 'so nothing more is recorded under it.' This differentiates it from sibling tools like tracesDelete (which likely deletes trace data, not configuration) and tracesCreateConfiguration. The purpose is specific and unambiguous.

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 description implies usage for stopping recording under a configuration, but does not explicitly mention when to use vs alternatives. Sibling tools such as tracesDelete or tracesCreateConfiguration exist, but no direct comparison or exclusion criteria are given. The usage context is inferred from the purpose rather than stated.

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

Deploy Server