Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateFunctionModule

Creates a new ABAP function module inside an existing function group, initializing it in initial state for further development.

Instructions

Create a new ABAP function module within an existing function group. Creates the function module 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
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

B3.4/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 disclosure burden. It adds one genuinely useful behavioral fact — the module is created 'in initial state' (implying activation is needed) — but omits transport/auth requirements, error behavior, and side effects on the parent group.

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 short sentences with no filler; the action and its scope come first, and the state note follows. Nothing is repeated from the tool name or schema.

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 no-output-schema creation tool the description covers the core action and the resulting state, and the schema carries all parameter documentation. It stops short of mentioning the required subsequent activation or transport concerns, which an agent would benefit from knowing.

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 five parameters (including detail, transport_request, description) are already documented in the schema. The description only echoes the required function-group relationship, adding no syntax or format detail beyond it. 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 ('Create a new ABAP function module') and scopes it to an existing function group. It is distinguishable from CreateFunctionGroup/CreateFunctionInclude by naming the artifact type, though it never explicitly contrasts with those siblings.

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?

Gives no when-to-use guidance, no prerequisites beyond the implied existence of a parent function group, and names no alternatives. An agent gets no signal about ordering relative to CreateFunctionGroup or the follow-up ActivateFunctionModule step.

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