Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev

bw_append_process_chain_dtp

Append a DTP load step to an existing process chain via in-place edit. Optionally add aDSO activation, choose predecessor, or auto-place at strand end. Skips if DTP already present.

Instructions

Append one DTP load step (optionally followed by its own DSO activation step) to an existing Process Chain (RSPC), via the BW/4HANA Cockpit REST API. In-place edit: reads the current model, appends the node(s)/edge(s)/inline variant, and PUTs it back — the caller does not supply the full model. By default it appends behind the strand end closest to the trigger (to keep strands balanced); pass predecessor to choose a node. edge_mode "both" (default) adds an on-success and an on-error edge per link ("always continue"); "success_only" adds only the on-success edge. Idempotent: if the DTP is already a node in the chain, it is skipped without writing. Optionally activates afterwards and then verifies that no collector was inserted and no extra strand appeared. A 412 on the PUT means the ETag was stale (chain modified between read and write); the error reports this explicitly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dtpYesDTP variant name to append (e.g. "DTP_NAME").
nameYesProcess chain technical name (e.g. "CHAIN_NAME"). Case-insensitive.
adsoactNoOptional aDSO name (e.g. "ADSO_NAME"). When given, an ADSOACT step activating this aDSO is added right after the DTP (per-DTP activation).
activateNoIf true, activate the chain immediately after the edit. Default false.
edge_modeNo"both" (default): add an on-success and an on-error edge per link. "success_only": add only the on-success edge.
predecessorNoNode to append behind: a DTP variant name, an aDSO whose ADSOACT node holds it, or the literal "strand_end_auto" (default). For "strand_end_auto" the terminal node closest to the trigger is chosen (ties → first).
transport_requestNoOptional transport request to record the change into. Only relevant when the chain is in a transportable package (not $TMP). If the chain is transportable and exactly one request is available, it is chosen automatically; pass this to disambiguate when several are available. Ignored for $TMP (local) chains.
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: in-place edit (read, modify, PUT), idempotency (skip if DTP exists), ETag handling (412 error explanation), optional activation/verification. No contradictions.

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 a single dense paragraph; it contains all necessary information but could be more scannable (e.g., bullet points). Still, it is front-loaded with the core action and is efficient.

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?

Given the complexity (7 parameters, many optional) and no output schema, the description covers all essential aspects: mechanism, defaults, idempotency, error handling, and optional behaviors. No gaps.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: explains default predecessor behavior, adsoact adds a step, activate includes verification, edge_mode options, and transport request handling. This goes beyond the schema's attribute descriptions.

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 the tool appends a DTP load step to an existing Process Chain, specifying the verb, resource, and mechanism (in-place edit via REST API). It distinguishes the tool from siblings like bw_swap_process_chain_dtp and bw_add_process_chain_program.

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

Usage Guidelines4/5

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

The description provides guidance on default behavior (append behind strand end closest to trigger), how to use predecessor, edge_mode options, and idempotency. It does not explicitly state when not to use the tool or compare to alternatives, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dnic-dev/bw-modeling-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server