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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ActivateFunctionGroup

Activates an ABAP function group by name, making its inactive version effective. Use it to publish pending function group changes in an SAP system.

Instructions

Activates the ABAP function group named by function_group_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": {
      "function_group_name": "<function_group_name>"
    },
    "name": "ActivateFunctionGroup"
  }
}

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
function_group_nameYesFunction group 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
    • 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"
+}
    • changedInput schema / properties / function_group_name / description
      Previous value: -"Function group name (e.g., Z_FG_TEST)."New value: +"Function group name."
  3. Addedv6.5.1

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 full burden and does meaningful work: it discloses that activation makes the inactive version live, and explains the non-obvious batch-mode recording semantics (recorded under a number, empty answer, retrieved later via BatchAnswers). It still omits error behavior when no inactive version exists and any permission/transport implications.

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, front-loaded with the core action; the second sentence is dense but earns its place by explaining batch-mode recording, though its phrasing ('Recordable', 'answers with empty content') is slightly compressed and could be clearer.

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?

A mutation tool with no annotations and no output schema needs to explain return shape and failure modes. The description covers the batch-answer retrieval path well but says nothing about the normal return content, errors, or what happens when no inactive version is pending.

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 both parameters are already documented, including the detail enum's terse/full/raw options. The description only echoes that function_group_name selects the target, adding no syntax or naming-convention guidance beyond the schema.

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 (activates) and resource (ABAP function group, named by parameter) plus the effect (inactive version goes into force). The resource boundary cleanly separates it from ActivateFunctionModule, ActivateProgram, ActivateClass and other Activate* siblings.

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 rather than stated: one infers this follows edits that produced an inactive version. It never says when to prefer it over ActivateObjects (the bulk activator) or when to run CheckFunctionGroup first, and no prerequisites 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