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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateMetadataExtension

Updates the source code of an existing ABAP Metadata Extension (DDLX) by locking it, applying changes, unlocking, and optionally activating it.

Instructions

Update source code of an existing ABAP Metadata Extension (DDLX). 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": "UpdateMetadataExtension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesMetadata Extension 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.
source_codeYesNew source code
transport_requestNoTransport request number (required for transportable packages), not a task.

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 (required for transportable packages)."New value: +"Transport request number (required for transportable packages), not a task."
  2. Changed1 schema field changed
    • addedInput schema / properties / transport_request
      Added value: +{
+  "description": "Transport request number (required for transportable packages).",
+  "type": "string"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description usefully discloses the mutation lifecycle: it locks, updates, unlocks, and optionally activates the object. It also notes that it runs outside batch mode, which is meaningful behavioral context. It stops short of covering failure behavior, permissions, or what happens if locking fails.

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 are front-loaded with the core purpose and then the important behavioral constraints. There is no wasted text.

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 six-parameter mutation tool with no annotations and no output schema, the description covers the essential operation and locking/activation behavior. It relies on the fully documented schema for parameter details, which is reasonable, though it could mention transport handling or failure semantics.

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 in the schema. The description adds only high-level context about locking and optional activation, without adding syntax or format meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: update the source code of an existing ABAP Metadata Extension (DDLX). It clearly distinguishes this tool from siblings such as CreateMetadataExtension, GetMetadataExtension, DeleteMetadataExtension, and ActivateMetadataExtension.

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?

The description makes clear the tool is for updating an existing DDLX and optionally activating it. However, it does not explicitly say when to use this versus ActivateMetadataExtension, CheckMetadataExtension, or UpdateDdl, nor does it describe prerequisites or exclusions.

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