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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

DeleteFunctionGroup

Deletes an ABAP function group from the SAP system through the ADT deletion API. Provide a transport request for transportable objects; local objects can be removed without one.

Instructions

Delete an ABAP function group from the SAP system via ADT deletion API. Transport request optional for local objects. 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": {
      "function_group_name": "<function_group_name>"
    },
    "name": "DeleteFunctionGroup"
  }
}

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
transport_requestNoTransport request number, not a task. Required for transportable objects. Optional for local objects.
function_group_nameYesFunctionGroup name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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: -"FunctionGroup name (e.g., Z_MY_FUNCTIONGROUP)."New value: +"FunctionGroup name."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required for transportable objects. Optional for local objects ($TMP)."New value: +"Transport request number, not a task. Required for transportable objects. Optional for local objects."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description must carry the whole burden. It does disclose two behavioral traits beyond the schema: transportability semantics and the fact that it runs outside batch mode (so BatchBegin wrappers will not apply). It omits irreversibility, permission/authorization needs, and what happens to contained function modules and includes.

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?

Three short sentences, front-loaded with the action and resource, each contributing information. "Runs outside batch mode" is slightly terse to the point of ambiguity about what mechanism it refers to, but nothing is wasted.

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 destructive tool with no annotations and no output schema, the description covers the operation and one key constraint but leaves the agent guessing about authorization, side effects on child objects, and the result shape. Adequate, 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 all three parameters are documented in the schema already, including the transport/orphan-object rule and the detail enum. The description's transport sentence largely repeats the schema, adding no syntax or format detail, 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 (delete) and resource (ABAP function group) plus the underlying mechanism (ADT deletion API), which cleanly separates it from DeleteFunctionModule, DeleteFunctionInclude, and DeleteProgram in the sibling list. It does not explicitly name or contrast with those siblings, 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?

"Transport request optional for local objects" and "Runs outside batch mode" give real preconditions, implying usage context. However, there is no explicit statement of when to prefer CheckFunctionGroup/GetFunctionGroup first, nor any warning about deleting a non-empty group or using this versus generic deletion flows.

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