Skip to main content
Glama
Sign In
mcp-abap-adt

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

DeleteUnitTest

Deletes the local ABAP Unit test classes for an existing ABAP class named by class_name while keeping the class itself, so you can remove test code without removing the production class.

Instructions

Deletes the ABAP Unit test classes of the ABAP class named by class_name. The class's local test classes are deleted, and the class stays. Runs outside batch mode.

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": {
      "class_name": "<class_name>"
    },
    "name": "DeleteUnitTest"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoHow much of the answer to return: "terse" (default, the fields you need to act), "full" (the whole parse), "raw" (the document as ADT sent it).terse
class_nameYesClass that holds the tests. Must already exist.
transport_requestNoTransport request, not a task. Required for a transportable object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv16.0.0
    • addedInput schema / properties / class_name
      Added value: +{
+  "description": "Class that holds the tests. Must already exist.",
+  "type": "string"
+}
    • addedInput schema / properties / detail
      Added value: +{
+  "default": "terse",
+  "description": "How much of the answer to return: \"terse\" (default, the fields you need to act), \"full\" (the whole parse), \"raw\" (the document as ADT sent it).",
+  "enum": [
+    "terse",
+    "full",
+    "raw"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / run_id
      Removed value: -{
-  "description": "Run identifier returned by CreateUnitTest/RunUnitTest.",
-  "type": "string"
-}
    • addedInput schema / properties / transport_request
      Added value: +{
+  "description": "Transport request, not a task. Required for a transportable object.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "run_id"
-]New value: +[
+  "class_name"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the destruction scope ('local test classes are deleted, and the class stays') and the execution mode ('outside batch mode'), but omits permissions/auth needs, reversibility, and whether deletion is confirmable.

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 compact sentences with the operation and its destruction scope front-loaded; every clause conveys substantive information with no filler.

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 3-param destructive tool with no output schema or annotations, the description adequately covers what is deleted, what is preserved, and the execution mode. It stops short of permissions/transport behavior and return details, so it's strong but not fully complete.

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 description coverage is 100%, so parameters are already well documented. The description only echoes class_name without adding format or constraints beyond the schema baseline, so a 3 applies.

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?

States a specific verb ('Deletes') and target ('the ABAP Unit test classes of the ABAP class named by class_name') and adds 'the class stays,' which distinguishes it from DeleteClass. It does not explicitly name the closely related sibling DeleteLocalTestClass, leaving some ambiguity about which to choose.

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?

The description offers no explicit when-to-use or when-not guidance. 'Runs outside batch mode' is a runtime constraint, not guidance on choosing this tool over alternatives like DeleteLocalTestClass or DeleteCdsUnitTest. Usage is only implied by the purpose.

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

Deploy Server

Other Tools