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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateFunctionInclude

Update the source code of an existing ABAP function group include, with options to activate the updated version and assign a transport request.

Instructions

Update source code of an existing ABAP function group include. Runs outside batch mode.

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>",
      "include_name": "<include_name>",
      "source_code": "<source_code>"
    },
    "name": "UpdateFunctionInclude"
  }
}

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
activateNoActivate the include after the source update. Default: false. Set true to make the updated source the active version immediately.
source_codeYesComplete ABAP include source code.
include_nameYesInclude name. Include must already exist.
transport_requestNoTransport request number, not a task. Required for transportable includes.
function_group_nameYesFunction group name containing the include.

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: -"Function group name containing the include (e.g., ZOK_FG_MCP01)."New value: +"Function group name containing the include."
    • changedInput schema / properties / include_name / description
      Previous value: -"Include name (e.g., LZOK_FG_MCP01F01). Include must already exist."New value: +"Include name. Include must already exist."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Required for transportable includes."New value: +"Transport request number, not a task. Required for transportable includes."
  2. Changed1 schema field changedv7.1.1
    • addedInput schema / properties / activate
      Added value: +{
+  "default": false,
+  "description": "Activate the include after the source update. Default: false. Set true to make the updated source the active version immediately.",
+  "type": "boolean"
+}
  3. Addedv7.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden for a mutation tool. It states that it updates existing source code and runs outside batch mode, but does not explain overwrite implications, activation behavior, transport handling, error conditions, or reversibility.

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?

The description is two compact sentences and front-loads the core action. Every sentence adds at least some useful information, with no repetition or unnecessary detail.

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?

The schema fully documents all six parameters, so the description need not repeat them. However, for a mutation tool with no annotations or output schema, it is only minimally complete: it omits important behavioral context such as whether the source is overwritten, the effect of activation, and transport requirements.

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 parameters are already well documented in the schema. The description only reinforces that the include must already exist and that source code is updated; it adds no further parameter semantics.

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?

The description gives a specific verb and resource: updating the source code of an existing ABAP function group include. The word 'existing' implicitly separates it from CreateFunctionInclude and DeleteFunctionInclude, though it does not explicitly name 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?

It provides no explicit guidance on when to use this tool versus alternatives such as CreateFunctionInclude, GetFunctionInclude, or UpdateFunctionModule. The only usage-related constraint is the brief note that it runs outside batch mode.

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