Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateInterface

Creates an initial ABAP interface object in an SAP system using an interface name and package, with optional description, language, and transport request.

Instructions

Create a new ABAP interface in SAP system. Creates the interface object in initial state.

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
descriptionNoInterface description. If not provided, interface_name will be used.
package_nameYesPackage name
interface_nameYesInterface name.
master_languageNoOptional master/original language for the created object (e.g. "EN", "DE", "ZH"). Defaults to the session language (SAP_LANGUAGE) or EN.
transport_requestNoTransport request number, not a task. Required for transportable packages.

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 / interface_name / description
      Previous value: -"Interface name (e.g., ZIF_TEST_INTERFACE_001). Must follow SAP naming conventions (start with Z or Y)."New value: +"Interface name."
    • 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."
  2. Changed1 schema field changedv8.1.0
    • 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"
+}
  3. Changed2 schema fields changed
    • removedInput schema / properties / activate
      Removed value: -{
-  "description": "Activate interface after creation. Default: true. Set to false for batch operations (activate multiple objects later).",
-  "type": "boolean"
-}
    • removedInput schema / properties / source_code
      Removed value: -{
-  "description": "Complete ABAP interface source code with INTERFACE...ENDINTERFACE section. If not provided, generates minimal template.",
-  "type": "string"
-}
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one real behavioral trait — the object is created "in initial state," implying a separate activation step — which is valuable. However it says nothing about required authorizations, the transport requirements implied by the transport_request parameter, or behavior when the interface already exists.

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 action and resource. The second sentence partly restates the first ("Creates the interface object"), but the "initial state" clause earns its place by adding a behavioral fact.

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 6-parameter mutation tool with no annotations and no output schema, the description covers the action and the resulting object state but omits the create/activate lifecycle, permission needs, and transport handling. That is minimally adequate for an experienced SAP agent but not self-sufficient.

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 schema already explains every parameter including the detail enum, master_language default, and the transport_request caveat. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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+resource ("Create a new ABAP interface in SAP system"), which cleanly separates it from GetInterface, UpdateInterface, and the many other Create* siblings. It stops short of explicitly naming its counterparts, so it lands just under the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of the natural follow-up (ActivateInterface) that a newly created ABAP object requires. The agent gets no help deciding between this and CreateClass/CreateFunctionGroup or understanding the create-then-activate workflow.

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