Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateTable

Update the DDL source code of an existing ABAP table. Locks, updates, unlocks, and optionally activates it.

Instructions

Update DDL source code of an existing ABAP table. 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 table after source update. Default: true.
ddl_codeYesComplete DDL source code for table. Example: '@EndUserText.label : \'My Table\' @AbapCatalog.tableCategory : #TRANSPARENT define table ztst_table { key client : abap.clnt not null; key id : abap.char(10); name : abap.char(255); }'
table_nameYesTable name. Table 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 / table_name / description
      Previous value: -"Table name (e.g., ZZ_TEST_TABLE_001). Table must already exist."New value: +"Table name. Table 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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose a key behavioral trait: it locks, updates, unlocks, and optionally activates the table, which tells the agent about side effects, state transitions, and that activation is optional. It omits auth/transport requirements and error behavior, but the lock/activate lifecycle is valuable disclosure beyond structured fields.

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 sentence fragments, front-loaded with the object of the update, zero waste. The lifecycle verbs are packed efficiently.

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 exists, but for a mutation tool the description covers what happens behaviorally (lock/update/unlock/activate) and the schema fully documents all five parameters with defaults and examples. Missing transport/authorization context and return promise keep it from a 5.

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 coverage is 100%, with enums, defaults, and examples already documented, so the baseline is 3. The description adds nothing about parameter syntax or interaction (e.g., how activate relates to activation tooling), so it does not exceed 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?

States a specific verb (Update) and resource (DDL source code of an existing ABAP table), and it is easily distinguished from siblings like UpdateDdl, UpdateStructure, and CreateTable. An agent can route correctly without opening the schema.

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 implies usage (update an existing table) but gives no explicit when-to-use guidance or alternatives, such as distinguishing it from UpdateDdl, UpdateStructure, or ActivateTable. 'Existing' and 'Table must already exist' in the schema are the only scoping hints.

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