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

mcp-abap-adt

by fr0ster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

GetEnhancements

Lists enhancement implementations for one or more ABAP objects, such as programs, includes, function groups, and classes, by object name and type.

Instructions

[read-only] Lists the enhancements (enhancement implementations) of the program, include, function group or class named by object_name and object_type. Takes object_name and object_type (one object: its enhancements) or objects (several objects: one entry per object, in the order given, each its enhancements answer or { object_name, object_type, error }). When object_type is one of CLASS, CLAS, CLAS/OC, FUNCTION_GROUP, FUNCTIONGROUP, FUGR, FUGR/F, PROGRAM, PROG, PROG/P and include_nested is any value but true, recordable: in batch mode a call is recorded under the next number and answers with empty content; its answer is read by number after the batch ends.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "GetEnhancements"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectsNo[read-only] Several objects, read together (give this or object_name and object_type)
object_nameNoName of the ABAP object (with object_type; or give objects)
object_typeNo[read-only] Type of the ABAP object

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv20.1.0
    • changedInput schema / properties / object_name / description
      Previous value: -"Name of the ABAP object"New value: +"Name of the ABAP object (with object_type; or give objects)"
    • addedInput schema / properties / objects
      Added value: +{
+  "description": "[read-only] Several objects, read together (give this or object_name and object_type)",
+  "items": {
+    "properties": {
+      "object_name": {
+        "description": "Name of the ABAP object",
+        "type": "string"
+      },
+      "object_type": {
+        "description": "Type of the ABAP object",
+        "type": "string"
+      }
+    },
+    "required": [
+      "object_name",
+      "object_type"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "object_name",
-  "object_type"
-]
  2. 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, the description carries the full behavioral burden. It declares the tool is [read-only] and discloses non-obvious batch behavior, including that calls can be recorded under the next number and answered with empty content. It does not describe permission requirements, the shape of the enhancement answer, or pagination, and it references include_nested even though that parameter is absent from the schema.

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?

The description is front-loaded with the tool's purpose and then covers input modes and batch behavior. It is dense but contains no filler; each sentence addresses a distinct concern. The long sentence about batch recording is harder to parse but still earns its place.

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?

There are no annotations and no output schema, so the description should be fairly complete. It covers read-only behavior, single vs multiple objects, and batch recording, but it does not describe the return shape of an enhancement answer or any permission constraints. The include_nested reference is also incomplete because that parameter is missing from the schema.

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 three parameters and the baseline is 3. The description adds useful mode semantics: single-object vs multi-object calls, ordering, and per-object error handling. However, the mention of include_nested, which is not in the schema, creates some ambiguity.

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?

The description states a specific verb and resource: it lists enhancement implementations for a named ABAP object. It clearly names the object kinds it works with (program, include, function group, class). However, it does not explicitly distinguish this tool from sibling tools such as GetEnhancementImpl or GetEnhancementSpot.

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 explains the two input modes: object_name plus object_type for one object, or objects for several objects. It does not say when to choose this tool over related enhancement or object-information tools, and it provides no exclusions or alternatives.

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