ABAP-ADT-API MCP-Server

activateObjects

Activate ABAP objects by providing object references with required properties like URI, type, name, and parent URI. Optionally perform pre-audit checks before activation.

Instructions

Activate ABAP objects using object references

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": {
      "objects": "<objects>"
    },
    "name": "activateObjects"
  }
}

Input Schema

Name	Required	Description	Default
`objects`	Yes	JSON array of objects to activate. Each object must have adtcore:uri, adtcore:type, adtcore:name, and adtcore:parentUri properties
`preauditRequested`	No	Whether to perform pre-audit checks

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Mar 20, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Activate ABAP objects', which implies a mutating operation, but lacks details about side effects, prerequisites, error handling, or reversibility. The preauditRequested parameter hints at optional checks, but this is not explained in the description.

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 a single sentence that is front-loaded with the verb 'Activate', contains no filler, and is appropriately concise. Every word contributes to the meaning.

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

Completeness2/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 is incomplete. It does not explain what the response contains, possible errors, activation order, or transport implications. The existence of similar sibling tools like activateByName suggests more differentiation guidance is needed.

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?

The input schema has 100% parameter description coverage, so parameters are already well documented. The description adds little beyond the phrase 'using object references', which aligns with the objects parameter. Since the schema carries the explanatory burden, a baseline score of 3 is appropriate.

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 'Activate ABAP objects using object references' clearly states the verb (activate), the target (ABAP objects), and the method (object references). This distinguishes it from sibling tool 'activateByName', which activates by name, making the purpose highly specific and unambiguous.

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 this tool is used when object references are available ('using object references'), which suggests a usage scenario but does not explicitly state when to use it over alternatives like activateByName. There is no explicit mention of exclusions or alternative tool selection, so guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server