Skip to main content
Glama
ethanhan2014

SAP ADT MCP Server

by ethanhan2014

delete_trace

Delete a specific runtime trace by providing its trace ID and optional system ID to clean up monitoring data in SAP systems.

Instructions

Delete a runtime trace

Input Schema

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

Implementation Reference

  • Registration of the 'delete_trace' tool in the ListToolsRequestSchema handler, defining its name, description, and input schema (trace_id required).
    {
      name: "delete_trace",
      description: "Delete a runtime trace",
      inputSchema: {
        type: "object" as const,
        properties: {
          trace_id: { type: "string", description: "Trace ID to delete" },
          ...SYSTEM_ID_PROP,
        },
        required: ["trace_id"],
      },
    },
  • The TraceIdSchema Zod schema used by delete_trace for input validation.
    const TraceIdSchema = z.object({ trace_id: z.string() });
  • Handler logic in CallToolRequestSchema switch that parses trace_id and calls client.deleteTrace(trace_id).
    case "delete_trace": {
      const { trace_id } = TraceIdSchema.parse(args);
      const result = await client.deleteTrace(trace_id);
      return { content: [{ type: "text", text: result }] };
    }
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as destructiveness, permission requirements, or side effects. For a delete operation, this is a significant gap.

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 a single concise sentence that conveys the core function. No unnecessary words, but could benefit from front-loading key constraints.

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

Completeness3/5

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

Given the tool's simplicity and full schema coverage, the description is minimally adequate. However, it lacks important context such as whether deletion is irreversible or if it requires specific permissions.

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?

Input schema has 100% description coverage for both parameters. The description does not add any additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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?

Description clearly states the verb 'Delete' and the resource 'runtime trace'. It is distinct from sibling tools like 'delete_trace_config' which deals with configurations, not traces.

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 on when to use this tool versus alternatives like 'delete_trace_config' or what happens if the trace is active. No context on prerequisites or consequences.

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