Skip to main content
Glama
fr0ster

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateClass

Modify source code of an existing ABAP class: locks, updates, unlocks, and optionally activates it.

Instructions

Update source code of an existing ABAP class. 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 after update. Default: false.
class_nameYesClass name.
source_codeYesComplete ABAP class source code.
transport_requestNoTransport request number, not a task. Required for transportable packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv16.0.0
    • changedInput schema / properties / class_name / description
      Previous value: -"Class name (e.g., ZCL_TEST_CLASS_001)."New value: +"Class name."
    • 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

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose the operation sequence: locks, updates, unlocks, and optional activation. However, it omits key behavioral facts such as whether the source replaces the entire class, permission requirements, and that transport_request may be mandatory for transportable packages.

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?

Two short sentences that are front-loaded with the core action, followed by the behavioral sequence. No filler, though the telegraphic lock/update/unlock list reads slightly like a changelog rather than agent guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description covers the mechanics but not the full picture: transport/permission prerequisites, error behavior, and what the operation returns are unaddressed. The schema does cover the parameters well, so the gap is behavioral rather than structural.

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 the schema already documents all five parameters including the activate flag, detail enum, and transport_request. The description only echoes the activation option ('optionally activates') without adding format or constraint detail, which matches the baseline 3 for schema-documented parameters.

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?

Names a specific verb (update) and resource (source code of an existing ABAP class), and the scope qualifier 'existing' separates it from CreateClass. It never names a sibling explicitly, but the Update/Create/Delete family pattern makes the distinction obvious from the name alone.

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?

Usage is only implied: 'existing' class signals this is for modification rather than creation, and 'optionally activates' hints that ActivateClass may not be needed separately. There is no explicit when-to-use, no prerequisites (e.g. transportable package requirements), and no when-not guidance.

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