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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateUnitTest

Rewrites an ABAP class's local test classes from provided source and activates the class, enabling updated unit tests to run outside batch mode.

Instructions

Writes test_class_source as the ABAP Unit test classes of the ABAP class named by class_name. The class's local test classes are rewritten, and the class is activated. 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>",
      "test_class_source": "<test_class_source>"
    },
    "name": "UpdateUnitTest"
  }
}

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.
test_class_sourceYesABAP source of the local test classes: definitions and implementations, FOR TESTING. Replaces what the include holds.
transport_requestNoTransport request, not a task. Required for a transportable object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / test_class_source
      Added value: +{
+  "description": "ABAP source of the local test classes: definitions and implementations, FOR TESTING. Replaces what the include holds.",
+  "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",
+  "test_class_source"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that local test classes are rewritten (a destructive replace), that the class is activated afterward, and that it runs outside batch mode. It omits permission/transport prerequisites, though transport_request is documented in the schema.

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 tight sentences with the resource, the destructive rewrite, activation, and batch-mode caveat front-loaded. Nothing is wasted.

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 mutation tool with no annotations and no output schema, the description covers the key behavioral facts (rewrite, activation, batch constraint). Minor gaps remain around prerequisites, but nothing essential for correct invocation 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 coverage is 100%, so all four parameters are already documented. The description references class_name and test_class_source meaningfully but adds no syntax or format detail beyond the schema, so baseline 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 (writes) and resource (ABAP Unit test classes of the named class), which clearly conveys the operation. It does not explicitly differentiate from close siblings like UpdateLocalTestClass or CreateUnitTest, so it stops short of a 5.

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 implied by the mutation verb and the 'must already exist' note carried by the schema, but the description offers no explicit when-to-use guidance or routing to alternatives such as UpdateLocalTestClass or CreateUnitTest.

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