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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

UpdateLocalDefinitions

Updates local definitions (class-local types/constants) in an ABAP class, handling lock, update, unlock, and optional parent class activation.

Instructions

Update local definitions (class-local types/constants) in an ABAP class. Manages lock, update, unlock, and optional activation of parent class. 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": {
      "class_name": "<class_name>",
      "definitions_code": "<definitions_code>"
    },
    "name": "UpdateLocalDefinitions"
  }
}

Input 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
class_nameYesParent class name.
definitions_codeYesUpdated source code for local definitions.
transport_requestNoTransport request number (required for transportable objects), not a task.
activate_on_updateNoActivate parent class after updating local definitions. Default: false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv16.0.0
    • changedInput schema / properties / activate_on_update / description
      Previous value: -"Activate parent class after updating. Default: false"New value: +"Activate parent class after updating local definitions. Default: false"
    • changedInput schema / properties / class_name / description
      Previous value: -"Parent class name (e.g., ZCL_MY_CLASS)."New value: +"Parent 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."New value: +"Transport request number (required for transportable objects), not a task."
  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 usefully discloses lock/update/unlock handling, optional parent-class activation, and that it runs outside batch mode. It does not explicitly state that existing definitions are overwritten or describe permission/transport requirements beyond what the schema already supplies.

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?

The description is three compact sentences with the core operation front-loaded, followed by lifecycle behavior and a runtime constraint. Every sentence contributes useful information without redundancy.

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 mutation tool with no annotations and no output schema, the description gives enough behavioral context about locking, updating, activation, and batch mode. It could say more about the response or overwrite semantics, but the schema covers parameters thoroughly.

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 parameter semantics are already well documented in the schema. The description mentions optional activation of the parent class, but adds little parameter meaning beyond the schema baseline.

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 local definitions in an ABAP class, with clarifying scope that these are class-local types/constants. This distinguishes it from sibling tools such as UpdateLocalTypes and DeleteLocalDefinitions.

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 usage context is implied by the purpose and the note that it runs outside batch mode, but the description does not explicitly say when to choose this tool over UpdateLocalTypes, UpdateLocalMacros, or GetLocalDefinitions. No explicit alternatives or when-not conditions are given.

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