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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateBehaviorDefinition

Update source code for an existing ABAP Behavior Definition while handling lock, unlock, and optional activation.

Instructions

Update source code of an existing ABAP Behavior Definition (BDEF). Locks, updates, unlocks, and optionally activates. 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": {
      "name": "<name>",
      "source_code": "<source_code>"
    },
    "name": "UpdateBehaviorDefinition"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBehavior Definition name
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 after update. Default: true
lock_handleNoLock handle from LockObject. If not provided, will attempt to lock internally (not recommended for stateful flows).
source_codeYesNew source code
transport_requestNoTransport request number, not a task. Required for transportable packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / 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. Changed1 schema field changed
    • addedInput schema / properties / transport_request
      Added value: +{
+  "description": "Transport request number (e.g., E19K905635). Required for transportable packages.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/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 discloses key behavior: locks, updates, unlocks, optional activation, and that it runs outside batch mode. It omits finer details such as failure behavior or permission requirements, but covers the core mutation workflow well.

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?

Three short sentences, front-loaded with the purpose, followed by behavioral notes. Every sentence adds useful information without repetition.

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?

The description gives enough context for an agent to understand the mutation workflow and activation side effect. Given full schema coverage and no output schema, remaining gaps such as transport handling and error responses are modest.

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 six parameters are already documented. The description adds only a reference to optional activation and the lock/update/unlock sequence; it does not add syntax or format details beyond the schema.

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 states a specific verb and resource: updating source code of an existing ABAP Behavior Definition. It clearly differentiates from creation/deletion/read tools by specifying 'existing' and 'source code', though it does not explicitly name sibling alternatives.

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?

It implies use for modifying existing BDEF source and notes optional activation, but provides no explicit when-to-use guidance versus ActivateBehaviorDefinition, CreateBehaviorDefinition, or CheckBehaviorDefinition. Usage is inferable but not directive.

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