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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Activate Multiple ABAP Objects

abap_activate_multiple
Idempotent

Activates multiple inactive ABAP objects in one call, skipping URLs outside the inactive worklist, releasing server-held locks first, and reporting success or failure.

Instructions

Activate several inactive ABAP objects in one call. Only URLs that match the inactive worklist (check_inactive_objects) are activated; others are skipped, and if none match nothing happens. Releases any lock this server holds on them first. Reports success or failure with messages, and warns when SAP says success but an object is still inactive. Use abap_activate for a single object.

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": {
      "urls": "<urls>"
    },
    "name": "abap_activate_multiple"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesADT object URLs exactly as check_inactive_objects lists them (e.g. ['/sap/bc/adt/oo/classes/zcl_order_api', '/sap/bc/adt/programs/programs/zreport'])
preauditNoRun pre-activation ATC checks. Default: false
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.2
    • changedInput schema / properties / urls / description
      Previous value: -"Array of ADT object URLs to activate"New value: +"ADT object URLs exactly as check_inactive_objects lists them (e.g. ['/sap/bc/adt/oo/classes/zcl_order_api', '/sap/bc/adt/programs/programs/zreport'])"
  2. First observedv1.16.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description discloses non-obvious behavior: non-matching URLs are silently skipped, a no-match call is a no-op, existing server-held locks are released first, and it warns when SAP reports success but the object remains inactive. Those are exactly the operational facts an agent cannot infer from structured fields.

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?

Four short sentences, each carrying distinct information: action, input constraint, side effects (lock release), and return/warning semantics. The alternative-tool pointer is placed last where it is most useful, and nothing is repeated from the schema or annotations.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so (success/failure messages plus a false-success warning). For a three-parameter, non-destructive batch mutation, nothing an agent needs to invoke it correctly is missing.

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 baseline is 3; the description earns a bump by adding meaning to urls beyond the schema's example — it must match the inactive worklist or it is skipped. The preaudit and connectionId parameters are left entirely to the schema, which is acceptable given full coverage.

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 opens with a specific verb and resource ("Activate several inactive ABAP objects in one call") and explicitly distinguishes itself from the single-object sibling abap_activate. It also scopes which URLs are actually actionable, so an agent knows exactly what this tool operates on.

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?

It gives the selecting condition (multiple objects vs. "abap_activate for a single object") and names the prerequisite source of inputs, check_inactive_objects. The stated skip behavior also implicitly tells the agent to source URLs from that worklist rather than constructing them freely.

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