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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ActivateInterface

Activate an ABAP interface by name so its inactive version becomes active in the SAP system, with terse, full, or raw response detail.

Instructions

Activates the ABAP interface named by interface_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": {
      "interface_name": "<interface_name>"
    },
    "name": "ActivateInterface"
  }
}

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
interface_nameYesInterface 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 / interface_name / description
      Previous value: -"Interface name (e.g., ZIF_MY_INTERFACE)."New value: +"Interface name."
  3. Addedv6.5.1

TDQS

A4/5.0
Behavior4/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 does disclose a genuinely non-obvious trait — that in batch mode the call is recorded under the next number and returns empty content, with the real answer retrieved later by number. It omits permissions, failure behavior, and whether dependent objects are also activated, leaving some gaps for a mutating tool.

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?

Two sentences, zero waste, with the core action and its effect front-loaded before the secondary batch-mode caveat.

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

Completeness4/5

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

For a two-parameter activation tool with no output schema, the description covers effect, target, and the batch-recording mechanic, which is enough to call it correctly. Minor gaps remain around prerequisites and error/partial-activation behavior.

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% and the detail parameter already documents its terse/full/raw enum meanings, so the schema does the heavy lifting. The description only restates interface_name ('the ABAP interface named by interface_name') and adds nothing about parameters.

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 a specific resource (the ABAP interface named by interface_name), and adds the effect ('its inactive version is in force'), which distinguishes it clearly from sibling Activate* tools for classes, tables, programs, etc.

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 by the activation semantics, but there is no explicit guidance on prerequisites (e.g., whether CheckInterface/GetInactiveObjects should precede it) or on choosing ActivateInterface over the generic ActivateObjects, and no statement of when not to use it.

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