mcp-abap-adt

CreateFunctionGroup

Creates a new ABAP function group in SAP, acting as a container for function modules. Provide a name and package to group related modules.

Instructions

Create a new ABAP function group in SAP system. Function groups serve as containers for function modules. When activate is false, 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>",
      "package_name": "<package_name>"
    },
    "name": "CreateFunctionGroup"
  }
}

Input Schema

Name	Required	Description	Default
`detail`	No	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).	terse
`activate`	No	Activate function group after creation. Default: true. Set to false for batch operations.
`description`	No	Function group description. If not provided, function_group_name will be used.
`package_name`	Yes	Package name
`master_language`	No	Optional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
`transport_request`	No	Transport request number, not a task. Required for transportable packages.
`function_group_name`	Yes	Function group name. Up to 26 characters.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv16.0.0Oct 4, 2026

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., ZTEST_FG_001). Must follow SAP naming conventions (start with Z or Y, max 26 chars)."New value: +"Function group name. Up to 26 characters."

changedInput schema / properties / package_name / description

Previous value: -"Package name (e.g., ZOK_LAB, $TMP for local objects)"New value: +"Package name"

changedInput schema / properties / transport_request / description

Previous value: -"Transport request number (e.g., E19K905635). Required for transportable packages."New value: +"Transport request number, not a task. Required for transportable packages."

Changed1 schema field changedv8.1.0Jun 26, 2026

addedInput schema / properties / master_language

Added value: +{
+  "description": "Optional master/original language for the created object (e.g. \"EN\", \"DE\", \"ZH\"). Defaults to the session language (SAP_LANGUAGE) or EN.",
+  "type": "string"
+}

First observedDec 29, 2025

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the non-obvious batch-recording behavior when activate is false, but omits what happens if the group already exists, whether the operation is destructive, permission/transport prerequisites, and any failure modes.

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?

Purpose is front-loaded in the first sentence, followed by a short clarifying clause and one batch-mode caveat. The batch sentence is slightly dense but every sentence contributes; nothing is padding.

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 7-parameter mutation tool with no annotations and no output schema, the description covers purpose and one behavioral quirk but leaves out creation-side outcomes (return shape, collision handling, transport application). It is usable but not 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 documented, and the description adds only marginal semantics by elaborating on the activate=false case that the schema touches on briefly. Baseline 3 applies.

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 ('Create a new ABAP function group in SAP system') and adds a definitional clause about function groups being containers for function modules. This clearly separates it from UpdateFunctionGroup, DeleteFunctionGroup, and GetFunctionGroup.

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?

The activate=false sentence implies a batch-usage context, giving some when-to-use signal, but there is no explicit routing against siblings (UpdateFunctionGroup for modification, CheckFunctionGroup for validation) and no prerequisites such as package/transport requirements.

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

Deploy Server