Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev

bw_update_adso

Modify an SAP BW aDSO by adding/removing fields, changing settings, managing key fields, or updating field properties, returning a lock handle for activation.

Instructions

Add/remove fields, change aDSO type/settings, manage key fields, or update individual field properties. action "add_field" (default): add one or more InfoObject-backed fields — infoobject_name required. action "remove_field": removes the field from the aDSO (and from the key if it was a key field). action "add_pure_field": add one or more pure (non-InfoObject) fields — pass fields array with name, label, data_type, optional length/precision/scale/aggregation_behavior/is_key. action "update_settings": change aDSO type preset and/or individual boolean flags — no infoobject_name needed. action "manage_keys": replace the complete key field list — pass key_fields array (empty = no key fields). action "update_field_properties": modify sidDeterminationMode, aggregationBehavior, fixedCurrency/Unit, a unit/currency field reference (unit_currency_field), or descriptions of a single field — pass field_name and properties. Returns a lock_handle that must be passed to bw_activate to complete the operation. Sequence: bw_update_adso → bw_activate (adso) → bw_activate (trfn) → bw_activate (each dtpa).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo"add_field" (default), "remove_field", "add_pure_field", "update_settings", "manage_keys", or "update_field_properties".
fieldsNoPure field definitions for action "add_pure_field".
settingsNoSettings to apply (only for action "update_settings").
adso_nameYesaDSO name (e.g. "ADSO_NAME").
transportNoTransport request number (e.g. DEVK900123). Only required if the BW system requires transport assignment.
field_nameNoField name to modify (only for action "update_field_properties"), e.g. "FIELD_NAME" or "AMOUNT_P".
key_fieldsNoList of field names that should be key fields (only for action "manage_keys"). Empty array removes all key fields.
propertiesNoField properties to update (only for action "update_field_properties").
infoobject_nameNoInfoObject name or comma-separated list to add or remove (e.g. "IOBJ_NAME" or "IOBJ_A,IOBJ_B"). Required for add_field and remove_field.
Behavior5/5

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

No annotations exist, so description carries full burden. It discloses that updates require a lock_handle and a specific activation sequence, describes the effect of remove_field on key fields, and notes transport requirements. This is comprehensive.

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 well-structured with action bullets and a sequence outline. It is somewhat lengthy but necessary for the tool's complexity. Could be slightly more concise by avoiding redundancy with schema descriptions.

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 9 parameters, nested objects, and no output schema, the description fully covers all actions, explains the lock_handle and activation chain, mentions transport, and provides examples in parameter descriptions. Very complete.

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 description adds significant meaning: explains defaults, constraints (e.g., pattern for UNIT, date fields), and action-specific parameter usage (e.g., key_fields for manage_keys). This goes beyond schema 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 modifies aDSO by listing multiple actions: add/remove fields, change type/settings, manage keys, update field properties. It distinguishes from sibling tools like bw_create_adso (creation) and bw_get_adso (reading).

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?

Each action is explained with its purpose and required parameters (e.g., add_field requires infoobject_name). The activation sequence is provided. However, it doesn't explicitly state when NOT to use this tool or mention alternatives for similar tasks.

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