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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

DeleteTable

Deletes an ABAP table from the SAP system via the ADT deletion API, with an optional transport request for transportable objects. Use it to remove tables no longer needed.

Instructions

Delete an ABAP table 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": {
      "table_name": "<table_name>"
    },
    "name": "DeleteTable"
  }
}

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

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 / table_name / description
      Previous value: -"Table name (e.g., Z_MY_TABLE)."New value: +"Table 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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does add two genuine operational facts beyond the schema: the transport requirement varies by object type, and the tool cannot run in batch mode. It omits the most consequential behaviors for a destructive operation — irreversibility, whether table data or dependent objects (data elements, DDL, CDS) block or cascade the deletion, and what permissions are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the verb and resource, with every clause adding information (API, transport rule, batch constraint). No filler or restatement of the tool name.

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?

There is no output schema and no annotations, so the description is the only source of behavioral detail for a destructive single-object operation. It is minimally viable but thin: it does not say what the response contains, whether the deletion is committed immediately, or how dependencies are handled.

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 all three parameters are already documented, including the transport/task distinction and the detail enum. The description's transport note duplicates rather than extends the schema, and table_name is left with only "Table name." Baseline 3 applies when the schema does the work.

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 table) plus the underlying mechanism (ADT deletion API), so the action is unambiguous. It does not explicitly contrast itself with siblings like DeleteStructure or DeleteDdl, but the resource noun is distinctive enough that an agent can differentiate them from the schemas alone.

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" imply preconditions and an execution constraint, so there is some implicit guidance. However, there is no explicit when-to-use vs. when-not, no mention of alternatives (e.g. DeleteStructure for structures), and no prerequisites such as object state or dependency checks.

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