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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateFunctionModule

Creates a new ABAP function module in an existing function group, returning it in initial state so you can begin implementation.

Instructions

Create a new ABAP function module within an existing function group. Creates the function module in initial state. 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": {
      "function_group_name": "<function_group_name>",
      "function_module_name": "<function_module_name>"
    },
    "name": "CreateFunctionModule"
  }
}

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
descriptionNoOptional description for the function module
transport_requestNoTransport request number, not a task. Required for transportable packages.
function_group_nameYesParent function group name
function_module_nameYesFunction module name. Up to 30 characters.

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: -"Parent function group name (e.g., ZTEST_FG_001)"New value: +"Parent function group name"
    • changedInput schema / properties / function_module_name / description
      Previous value: -"Function module name (e.g., Z_TEST_FUNCTION_001). Must follow SAP naming conventions (start with Z or Y, max 30 chars)."New value: +"Function module name. Up to 30 characters."
    • 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. Changed3 schema fields changed
    • removedInput schema / properties / activate
      Removed value: -{
-  "default": true,
-  "description": "Whether to activate the function module after creation (default: true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / source_code
      Removed value: -{
-  "description": "ABAP source code for the function module including signature (FUNCTION name IMPORTING/EXPORTING ... ENDFUNCTION).",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "function_group_name",
-  "function_module_name",
-  "source_code"
-]New value: +[
+  "function_group_name",
+  "function_module_name"
+]
  3. First observed

TDQS

A3.7/5.0
Behavior4/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 discloses that the module is created in 'initial state' and explains batch-mode recording semantics in detail—both valuable beyond the schema. It omits permission requirements, duplicate-name error behavior, and transport implications (though transport is covered in the schema).

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 sentences, front-loaded with the core purpose. The batch-mode note is longer but relevant. There is no wasted language, though the third sentence could be tightened slightly.

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 create mutation with no annotations and no output schema, the description covers purpose, initial state, and batch behavior adequately. It leaves error handling and authorization unstated, but the fully documented schema handles all parameter 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% with all five parameters documented, so the baseline is 3. The description adds no parameter-level detail beyond what the schema already provides.

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 ('Create') and resource ('new ABAP function module') scoped 'within an existing function group'. This inherently distinguishes it from sibling creators like CreateFunctionGroup and CreateFunctionInclude, even though it does not name them explicitly.

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?

No explicit when-to-use or alternative guidance. The phrase 'within an existing function group' implies a prerequisite, but the description never says when to choose this over UpdateFunctionModule or CreateFunctionInclude, nor does it list exclusions.

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