Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateStructure

Update DDL source code for an existing ABAP structure by locking, applying changes, unlocking, and optionally activating it in SAP.

Instructions

Update DDL source code of an existing ABAP structure. 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 structure after source update. Default: true.
ddl_codeYesComplete DDL source code for structure. Example: '@EndUserText.label : \'My Structure\' @AbapCatalog.tableCategory : #TRANSPARENT define structure zz_s_test_001 { client : abap.clnt not null; id : abap.char(10); name : abap.char(255); }'
structure_nameYesStructure name. Structure must already exist.
transport_requestNoTransport request number, not a task. Optional if object is local or already in transport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / structure_name / description
      Previous value: -"Structure name (e.g., ZZ_S_TEST_001). Structure must already exist."New value: +"Structure name. Structure must already exist."
    • changedInput schema / properties / transport_request / description
      Previous value: -"Transport request number (e.g., E19K905635). Optional if object is local or already in transport."New value: +"Transport request number, not a task. Optional if object is local or already in transport."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the meaningful lifecycle: "Locks, updates, unlocks, and optionally activates." That is genuine behavioral context beyond the schema. However, it omits failure/recovery behavior (is the lock released if the update fails?), permission requirements, and transport implications for a mutation on a persisted object.

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 short sentences, front-loaded with the verb and resource, followed immediately by the operational behavior. No filler, no redundancy, nothing an agent has to skip past.

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?

With a rich 5-parameter schema at 100% coverage and no output schema, the description needs mainly to convey the action and its side effects, which the lock/update/unlock/activate sentence does. It is close to sufficient for a mutation tool, but with zero annotations it could reasonably say more about safety and authorization before the agent invokes it.

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 every parameter including structure_name, ddl_code, activate, detail, and transport_request is already documented in the schema with examples and defaults. The description's phrase "optionally activates" only restates what the activate parameter already declares, adding no new meaning. Baseline 3 is appropriate.

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: "Update DDL source code of an existing ABAP structure." An agent can distinguish this from UpdateTable, UpdateDdl, and CreateStructure without opening a schema. It stops short of naming which sibling to prefer in a given situation, but the purpose 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The description does not explain how this differs from UpdateTable or UpdateDdl, nor how the implicit activation interacts with the sibling ActivateStructure. The only precondition (structure must already exist) lives in the schema, not the description.

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