Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

bw_activate

Activate a BW object after updating. Provide the lock handle, or an empty string for DTP/DataSource. Auto-unlock, then re-activate any deactivated DTPs shown in the response.

Instructions

Activate one BW object (aDSO, Transformation, DTP, InfoObject, InfoSource, DataSource, CompositeProvider, or Aggregation Level). 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, and for an Aggregation Level (alvl) created with bw_create_aggregation_level.
object_nameYesObject name (e.g. "OBJECT_NAME" or "DTP_..."). For rsds, the DataSource name.
object_typeYesObject type: adso, trfn, dtpa, iobj, trcs, rsds (DataSource), hcpr (CompositeProvider), or alvl (Aggregation Level).
source_systemNoSource system name. Required when object_type is "rsds" (e.g. "LSYS_NAME").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv1.4.0
    • changedInput schema / properties / lock_handle / description
      Previous value: -"Lock handle from bw_update_adso or bw_update_transformation. Use empty string \"\" for DTP and DataSource (rsds) activation."New value: +"Lock handle from bw_update_adso or bw_update_transformation. Use empty string \"\" for DTP and DataSource (rsds) activation, and for an Aggregation Level (alvl) created with bw_create_aggregation_level."
    • changedInput schema / properties / object_type / description
      Previous value: -"Object type: adso, trfn, dtpa, iobj, trcs, rsds (DataSource), or hcpr (CompositeProvider)."New value: +"Object type: adso, trfn, dtpa, iobj, trcs, rsds (DataSource), hcpr (CompositeProvider), or alvl (Aggregation Level)."
    • changedInput schema / properties / object_type / enum
      Previous value: -[
-  "adso",
-  "trfn",
-  "dtpa",
-  "iobj",
-  "trcs",
-  "rsds",
-  "hcpr"
-]New value: +[
+  "adso",
+  "trfn",
+  "dtpa",
+  "iobj",
+  "trcs",
+  "rsds",
+  "hcpr",
+  "alvl"
+]
  2. Changed5 schema fields changedv0.9.1
    • changedInput schema / properties / lock_handle / description
      Previous value: -"Lock handle from bw_update_adso or bw_update_transformation. Use empty string \"\" for DTP activation."New value: +"Lock handle from bw_update_adso or bw_update_transformation. Use empty string \"\" for DTP and DataSource (rsds) activation."
    • changedInput schema / properties / object_name / description
      Previous value: -"Object name (e.g. \"OBJECT_NAME\" or \"DTP_...\")."New value: +"Object name (e.g. \"OBJECT_NAME\" or \"DTP_...\"). For rsds, the DataSource name."
    • changedInput schema / properties / object_type / description
      Previous value: -"Object type: adso, trfn, dtpa, iobj, or trcs."New value: +"Object type: adso, trfn, dtpa, iobj, trcs, rsds (DataSource), or hcpr (CompositeProvider)."
    • changedInput schema / properties / object_type / enum
      Previous value: -[
-  "adso",
-  "trfn",
-  "dtpa",
-  "iobj",
-  "trcs"
-]New value: +[
+  "adso",
+  "trfn",
+  "dtpa",
+  "iobj",
+  "trcs",
+  "rsds",
+  "hcpr"
+]
    • addedInput schema / properties / source_system
      Added value: +{
+  "description": "Source system name. Required when object_type is \"rsds\" (e.g. \"LSYS_NAME\").",
+  "type": "string"
+}
  3. First observedv0.7.0

TDQS

A4.4/5.0
Behavior4/5

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

There are no annotations, so the description carries the full behavioral burden. It discloses that unlock is sent automatically, except for DTPs and DataSources, and that impact analysis can deactivate DTPs that must be re-activated. This is strong side-effect transparency, though error behavior is not covered.

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 efficiently organized and every sentence contributes: scoping sentence, lock-handle rules, source-system rule, and a side-effect warning. There is no filler or redundant text.

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 five-parameter tool without an output schema, the description covers the nu rules, provides usage conditions, notes side effects, and warns about required re-activations. It does not describe the exact success/error return shape, but the essential calling requirements are covered.

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%, giving a baseline of 3. The description adds real value beyond the schema by explaining when lock_handle must be empty, when source_system is required, and how unlock behavior varies by object type.

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 starts with a specific verb and resource: 'Activate one BW object' and lists the exact supported object types. This clearly distinguishes it from sibling tools like bw_activate_request and bw_activate_process_chain.

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 gives concrete usage rules: when to pass a lock_handle, when to pass an empty string, and when to include source_system. It does not explicitly name alternative tools for request or process-chain activation, but the object-type enumeration makes the intended scope 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