Skip to main content
Glama
Freight-Art

abapsmith

by Freight-Art
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

abap_activate

Destructive

Checks, activates, or formats ABAP development objects on a live SAP system via ADT, with batch and package activation support.

Instructions

mode=check: syntax check, no lock. mode=activate: check then activate. mode=format: pretty-print (source=text, or object=format-and-save).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoDefault activate. format pretty-prints ABAP source: `source` alone formats text (no write), `object` alone formats and saves the object if it changed — never both.
typeNoADT type, e.g. CLAS/OC. Also names the type of an inline `source` draft when `object` is omitted (mode=check only): PROG/P, CLAS/OC or INTF/OI.
objectNoObject reference. Required unless `objects` (batch), `package` (package activation), or the inline form (mode=check with `type` + `source`, no server object).
sourceNoWith `object`: draft to check/activate for that object. mode=check without `object`: the draft to check inline (needs `type`). Or text to format.
affectsNoRequired to activate ENHO/XH or ENHS/XS.
corr_nrNoTransport request. $TMP needs none. Not for text format, `objects` or `package`.
objectsNoBatch activate, 2+ objects; omit `object`. mode=activate only.
packageNomode=activate only: activate every inactive object of this package (your own inactive worklist, intersected with the package contents) in one activation request. Not combinable with `object`, `objects`, `type`, `source`, `affects`.
recursiveNoWith `package`: also include sub-packages (depth-capped).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.6.36
    • changedInput schema / properties / corr_nr / description
      Previous value: -"Transport request. $TMP needs none. Not for text format."New value: +"Transport request. $TMP needs none. Not for text format, `objects` or `package`."
    • changedInput schema / properties / object / description
      Previous value: -"Object reference."New value: +"Object reference. Required unless `objects` (batch), `package` (package activation), or the inline form (mode=check with `type` + `source`, no server object)."
    • addedInput schema / properties / package
      Added value: +{
+  "description": "mode=activate only: activate every inactive object of this package (your own inactive worklist, intersected with the package contents) in one activation request. Not combinable with `object`, `objects`, `type`, `source`, `affects`.",
+  "type": "string"
+}
    • addedInput schema / properties / recursive
      Added value: +{
+  "description": "With `package`: also include sub-packages (depth-capped).",
+  "type": "boolean"
+}
    • changedInput schema / properties / source / description
      Previous value: -"Unsaved draft to check/activate, or text to format."New value: +"With `object`: draft to check/activate for that object. mode=check without `object`: the draft to check inline (needs `type`). Or text to format."
    • changedInput schema / properties / type / description
      Previous value: -"ADT type, e.g. CLAS/OC."New value: +"ADT type, e.g. CLAS/OC. Also names the type of an inline `source` draft when `object` is omitted (mode=check only): PROG/P, CLAS/OC or INTF/OI."
  2. Changed4 schema fields changedv0.6.2
    • changedInput schema / properties / corr_nr / description
      Previous value: -"Transport request. $TMP needs none."New value: +"Transport request. $TMP needs none. Not for text format."
    • changedInput schema / properties / mode / description
      Previous value: -"Default activate."New value: +"Default activate. format pretty-prints ABAP source: `source` alone formats text (no write), `object` alone formats and saves the object if it changed — never both."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "check",
-  "activate"
-]New value: +[
+  "check",
+  "activate",
+  "format"
+]
    • changedInput schema / properties / source / description
      Previous value: -"Unsaved draft to check/activate."New value: +"Unsaved draft to check/activate, or text to format."
  3. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description adds important behavioral context: mode=check does no lock, format with source alone does no write, format with object saves if changed, and package activation operates on the user's own inactive worklist. This goes beyond the annotations by explaining side effects and constraints.

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 compact and front-loaded with the mode semantics. It packs a lot of information into a few sentences without redundancy. Slightly dense for a first read, but every sentence earns its place.

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 complex 9-parameter tool with nested objects and no output schema, the description covers the key modes, constraints, and exclusions. It doesn't explain return values or error behavior, but the schema already covers parameter details. The main gap is lack of guidance on what the response looks like, but that's not required given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description adds value by explaining mode semantics and the inline draft form (mode=check with type + source), which is not fully obvious from the schema alone. However, most parameter meaning is already in the schema, so the description's incremental contribution is moderate.

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 clearly states three distinct modes (check, activate, format) with specific verbs and resources. It distinguishes the tool's purpose from siblings like abap_read, abap_write, and abap_rap by focusing on activation/check/format operations on ABAP objects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly states when to use each mode and what combinations are valid/invalid (e.g., 'never both', 'mode=activate only', 'Not combinable with'). It also clarifies when alternatives like batch activation or package activation apply, giving clear routing 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