Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

RunUnitTest

Execute ABAP Unit tests for a specified class and return the results, with detail levels terse, full, or raw.

Instructions

Run the ABAP Unit tests of a class and return the result.

Input Schema

TableJSON 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 whose tests run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv16.0.0
    • addedInput schema / properties / class_name
      Added value: +{
+  "description": "Class whose tests run.",
+  "type": "string"
+}
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Optional context string shown in SAP tools.",
-  "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 / duration
      Removed value: -{
-  "properties": {
-    "long": {
-      "type": "boolean"
-    },
-    "medium": {
-      "type": "boolean"
-    },
-    "short": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}
    • removedInput schema / properties / risk_level
      Removed value: -{
-  "properties": {
-    "critical": {
-      "type": "boolean"
-    },
-    "dangerous": {
-      "type": "boolean"
-    },
-    "harmless": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}
    • removedInput schema / properties / scope
      Removed value: -{
-  "properties": {
-    "add_foreign_tests_as_preview": {
-      "type": "boolean"
-    },
-    "foreign_tests": {
-      "type": "boolean"
-    },
-    "own_tests": {
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}
    • removedInput schema / properties / tests
      Removed value: -{
-  "description": "List of container/test class pairs to execute.",
-  "items": {
-    "properties": {
-      "container_class": {
-        "description": "Class that owns the test include (e.g., ZCL_MAIN_CLASS).",
-        "type": "string"
-      },
-      "test_class": {
-        "description": "Test class name inside the include (e.g., LTCL_MAIN_CLASS).",
-        "type": "string"
-      }
-    },
-    "required": [
-      "container_class",
-      "test_class"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / title
      Removed value: -{
-  "description": "Optional title for the ABAP Unit run.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "tests"
-]New value: +[
+  "class_name"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says tests run and a result returns. It omits whether the run is read-only, whether it can be long-running, whether it requires the object to be activated, and what failure/timeout behavior looks like.

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?

A single front-loaded sentence with no filler; the verb and scope appear immediately. It is efficiently sized, though it is arguably a touch thin rather than padded.

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?

For a two-parameter tool with no output schema, the description is serviceable but thin: it does not hint at what 'the result' contains (pass/fail counts, messages) or that the detail parameter controls response depth. An agent can call it, but context around the run result 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?

Schema description coverage is 100%, with both class_name and the detail enum fully documented in the schema itself, so the baseline is 3. The description adds no syntax, format, or selection guidance beyond what the schema already supplies.

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 and resource ('Run the ABAP Unit tests of a class') and returns a result, which cleanly scopes it against the sibling unit-test runners (RunCdsUnitTest, RunFunctionGroupUnitTest, RunFunctionModuleUnitTest) by naming the object type. It stops short of explicitly naming those alternatives, but the 'of a class' scope already differentiates it.

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?

Usage is only implied: an agent can infer it runs tests on an existing class, but there is no statement of prerequisites (e.g. class must exist/be active) or when to prefer it over the CDS/function-group/function-module variants. No exclusions or alternatives are given.

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