Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev

bw_activate

Activate BW objects (aDSO, Transformation, DTP, etc.) using a lock handle; use empty for DTP/DataSource. Automatically unlocks and lists DTPs deactivated by impact analysis, which must be reactivated.

Instructions

Activate one BW object (aDSO, Transformation, DTP, InfoObject, InfoSource, DataSource, or CompositeProvider). Pass the lock_handle from bw_update_adso or bw_update_transformation. For DTP and DataSource (rsds) activation use lock_handle="" (no lock needed — standalone activation). For object_type "rsds" also pass source_system (a DataSource is identified by DataSource name plus source system). Unlock is sent automatically after activation (not for DTPs or DataSources). The response lists any DTPs deactivated by impact analysis — these must be re-activated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transportNoTransport request number. Required on systems with transport obligation.
lock_handleYesLock handle from bw_update_adso or bw_update_transformation. Use empty string "" for DTP and DataSource (rsds) activation.
object_nameYesObject name (e.g. "OBJECT_NAME" or "DTP_..."). For rsds, the DataSource name.
object_typeYesObject type: adso, trfn, dtpa, iobj, trcs, rsds (DataSource), or hcpr (CompositeProvider).
source_systemNoSource system name. Required when object_type is "rsds" (e.g. "LSYS_NAME").
Behavior4/5

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

Discloses automatic unlock behavior (except DTP/DataSource) and that response lists deactivated DTPs requiring re-activation. Since no annotations are provided, this description carries the full burden and covers important behavioral traits.

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 main purpose and is concise given the complexity. It could be slightly shorter, but every sentence adds necessary detail without redundancy.

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?

Covers prerequisites, special cases, response content, and object types. No output schema is provided, so the description of the response (deactivated DTPs) helps fill the gap. Parameter and usage details are comprehensive.

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?

All 5 parameters are described in the schema (100% coverage). The description adds value by explaining lock_handle usage (source and empty string condition) and source_system requirement for rsds, going beyond schema definitions.

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 clearly states the tool activates one BW object and lists supported object types. It distinguishes from siblings like bw_activate_process_chain implicitly, but does not explicitly contrast, leaving some ambiguity.

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 provides prerequisites (lock_handle from update tools) and special case handling (empty lock for DTP/DataSource). However, it does not explicitly state when to use this tool versus sibling activation tools (e.g., bw_activate_process_chain).

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