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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ActivateClass

Activates a specified ABAP class, making its inactive version active so the intended changes take effect.

Instructions

Activates the ABAP class named by class_name, so its inactive version is in force. Recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

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

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 name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv20.1.0
    • removedInput schema / properties / session_id
      Removed value: -{
-  "description": "Session ID from GetSession. If not provided, a new session will be created.",
-  "type": "string"
-}
    • removedInput schema / properties / session_state
      Removed value: -{
-  "description": "Session state from GetSession (cookies, csrf_token, cookie_store). Required if session_id is provided.",
-  "properties": {
-    "cookie_store": {},
-    "cookies": {
-      "type": "string"
-    },
-    "csrf_token": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
  2. Changed2 schema fields changedv16.0.0
    • changedInput schema / properties / class_name / description
      Previous value: -"Class name (e.g., ZCL_MY_CLASS)."New value: +"Class name."
    • 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"
+}
  3. Addedv6.5.1

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose a non-obvious behavior: in batch mode the call is recorded under a sequence number and returns empty content that must be read later via BatchAnswers. That is genuinely useful beyond the schema. It still omits error/permission behavior and whether an already-active class fails, which keeps it below a 5.

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?

Two sentences, and the core action is front-loaded before the batch caveat. The second sentence is dense and slightly convoluted ('recorded under the next number and answers with empty content'), but every clause carries information an agent needs.

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 two-parameter mutation tool with no annotations and no output schema, the definition covers the action, its effect, and the batch-mode return convention. Missing pieces are failure modes and confirmation of what the activation response contains, but nothing critical to calling it correctly is absent.

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 the schema already documents both class_name and the detail enum with its three modes. The description only restates that class_name names the class and adds nothing about the detail parameter. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Activates the ABAP class') plus the effect ('its inactive version is in force'), which is exactly what distinguishes it from the many Activate* siblings such as ActivateProgram or ActivateInterface. An agent can identify the target object type and outcome without opening the schema.

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 effect statement — you call it when a class has an inactive version that should be put in force — and the batch-mode sentence gives a real usage context. However, it never states prerequisites (an inactive version must exist), what happens if the class is already active, or points to any alternative such as ActivateObjects for multi-object activation.

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