Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateFunctionModule

Update the source code of an existing ABAP function module, handling locking, updating, unlocking, and optional activation.

Instructions

Update source code of an existing ABAP function module. Locks, updates, unlocks, and optionally activates.

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
activateNoActivate function module after source update. Default: false. Set to true to activate immediately.
source_codeYesComplete ABAP function module source code, from FUNCTION to ENDFUNCTION.
transport_requestNoTransport request number, not a task. Required for transportable function modules.
function_group_nameYesFunction group name containing the function module.
function_module_nameYesFunction module name. Function module must already exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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: -"Function group name containing the function module (e.g., ZOK_FG_MCP01)."New value: +"Function group name containing the function module."
    • changedInput schema / properties / function_module_name / description
      Previous value: -"Function module name (e.g., Z_TEST_FM_MCP01). Function module must already exist."New value: +"Function module name. Function module must already exist."
    • changedInput schema / properties / source_code / description
      Previous value: -"Complete ABAP function module source code. Must include FUNCTION statement with parameters and ENDFUNCTION. Example:\n\nFUNCTION Z_TEST_FM\n  IMPORTING\n    VALUE(iv_input) TYPE string\n  EXPORTING\n    VALUE(ev_output) TYPE string.\n  \n  ev_output = iv_input.\nENDFUNCTION."New value: +"Complete ABAP function module source code, from FUNCTION to ENDFUNCTION."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required for transportable function modules."New value: +"Transport request number, not a task. Required for transportable function modules."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the operation sequence: locks, updates, unlocks, and optionally activates. This is meaningful behavioral detail beyond the schema. It omits permission requirements, reversibility, and transport implications (though transport_request is documented in schema).

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 compact sentences with the core purpose front-loaded and the behavioral sequence second. Every clause earns its place; nothing is redundant or padded.

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?

Given no annotations and no output schema, the description covers the mutation behavior adequately but stops short of the prerequisites an agent would want: transport requirement context, error conditions, and what a lock failure means. Adequate but with clear gaps for a mutation tool.

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 the schema already documents all six parameters including the detail enum default and the activate flag. The description adds no parameter-level detail beyond this, so the baseline of 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 (update) and resource (source code of an existing ABAP function module), with 'existing' implicitly distinguishing it from CreateFunctionModule. It does not explicitly name any sibling, but the operation is unambiguous.

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 'existing function module' and the optional activation, which hints at the ActivateFunctionModule sibling, but no explicit when/when-not or alternative routing is given. An agent can infer the context but gets no guidance on prerequisites or when to prefer ActivateFunctionModule.

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