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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CreateFunctionInclude

Creates a new ABAP include within an existing function group in initial state, enabling reusable ABAP code to be added to that group.

Instructions

Create a new ABAP include within an existing function group. Creates the include 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>",
      "include_name": "<include_name>"
    },
    "name": "CreateFunctionInclude"
  }
}

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 include
include_nameYesInclude name.
transport_requestNoTransport request number, not a task. Required for transportable packages.
function_group_nameYesParent function group name

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 / include_name / description
      Previous value: -"Include name (e.g., LZTEST_FG_001F01)."New value: +"Include 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. Addedv7.1.0

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 yet does add non-obvious traits: the include is created in initial (inactive) state, and the recording/empty-response batch semantics are disclosed. It stops short of stating permission/transport prerequisites or failure conditions (e.g., if the include 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?

Front-loads the core action in the first sentence, then adds the initial-state and batch semantics. Efficient overall, though the batch sentence is somewhat dense jargon that could confuse without batch context.

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?

No output schema and no annotations, so the description must carry context; it covers creation, initial state, and batch recording. Missing only peripheral details (activation follow-up, transport prerequisites, behavior on name collision), which keeps it just under fully complete.

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 the detail enum and transport_request) are already documented in the schema. The description adds no parameter-level detail beyond what is structured; 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 an ABAP include) scoped to an existing function group. Clear what it does; it does not explicitly name UpdateFunctionInclude/DeleteFunctionInclude as alternatives, but the create vs. update/delete intent is unambiguous from the verb.

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?

Implies usage (creating a new include inside an existing function group), and the batch-mode sentence gives some context. However there is no explicit when-to-use / when-not-to-use guidance relative to siblings, nor prerequisites (e.g., function group must exist, transport requirements).

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