Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

DeleteFunctionModule

Deletes an ABAP function module from an SAP system via the ADT deletion API. Supply the module and function group names; add a transport request for transportable objects.

Instructions

Delete an ABAP function module from the SAP system via ADT deletion API. Transport request optional for local objects.

Input Schema

TableJSON 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 containing the function module.
function_module_nameYesFunctionModule name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 containing the function module (e.g., Z_MY_FUNCTIONGROUP)."New value: +"FunctionGroup name containing the function module."
    • changedInput schema / properties / function_module_name / description
      Previous value: -"FunctionModule name (e.g., Z_MY_FUNCTIONMODULE)."New value: +"FunctionModule 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. Changed2 schema fields changed
    • addedInput schema / properties / function_group_name
      Added value: +{
+  "description": "FunctionGroup name containing the function module (e.g., Z_MY_FUNCTIONGROUP).",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "function_module_name"
-]New value: +[
+  "function_module_name",
+  "function_group_name"
+]
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a destructive operation. It discloses the transport-request nuance but says nothing about irreversibility, whether the deletion can be undone, required authorizations, or what happens on failure for a tool that permanently removes an object.

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 short sentences, front-loaded with the verb and resource, with no filler. Efficiency is good, though the second sentence is somewhat redundant with the schema's transport_request description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-annotated tool with no output schema, the description is thin: it omits irreversibility, authorization requirements, and error/return behavior. The transport note is useful but does not compensate for the missing safety and failure semantics.

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 four parameters are documented in the schema itself, including the transport_request local/transportable distinction. The description merely restates that transport nuance rather than adding syntax, format, or constraints beyond the schema, so the 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 and resource (delete an ABAP function module) plus the mechanism (ADT deletion API), which cleanly separates it from siblings like DeleteFunctionGroup and DeleteFunctionInclude. It stops short of explicitly naming those siblings as alternatives, so it falls just 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?

The only usage signal is that the transport request is optional for local objects, which implies when a transport is needed. There is no explicit when-to-use guidance, no discussion of alternatives (e.g. deactivating vs deleting), and no stated prerequisites or confirmation expectations.

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