Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_update_infoobject

Update an InfoObject's description, lower-case flag, or attribute list; for key figures, set fixed unit or currency. Replaces attributes only when supplied, and handles lock-activate-unlock in one call.

Instructions

Update a Characteristic InfoObject: change description, the lower case flag, and/or replace the attribute list. Supplying attributes replaces all existing ones (pass an empty array to remove all); omitting them leaves the list untouched. Also supports Key Figure (KYF) updates: set fixed_unit or fixed_currency. Sequence: lock → GET → PUT → activate → unlock — all in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInfoObject name (e.g. "IOBJ_NAME").
transportNoWorkbench transport order number (e.g. "DEVK900000"). Required when object is in a non-local package.
attributesNoNew attribute list, replacing all existing ones. Pass [] to remove all attributes; omit to leave them unchanged.
fixed_unitNoKYF only. Fixed unit of measure (e.g. "KWH", "M3"). Sets fixedUnit on a QUAN key figure.
lower_caseNoCHA only. Allow lower case letters (RSDCHABAS-LOWERCASE). Omit to keep existing. Set true for characteristics whose values may contain lower case letters or characters outside the permitted character set (RSKC), such as umlauts. Changing the flag on a characteristic already used by a provider that holds data is accepted; a load that failed activation on such a value can then simply be activated again.
descriptionNoNew short and long description text. Omit to keep existing.
fixed_currencyNoKYF only. Fixed currency (e.g. "EUR"). Sets fixedCurrency on a CURR key figure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.0
    • changedInput schema / properties / attributes / description
      Previous value: -"New attribute list. Omit or pass [] to remove all attributes."New value: +"New attribute list, replacing all existing ones. Pass [] to remove all attributes; omit to leave them unchanged."
    • addedInput schema / properties / lower_case
      Added value: +{
+  "description": "CHA only. Allow lower case letters (RSDCHABAS-LOWERCASE). Omit to keep existing. Set true for characteristics whose values may contain lower case letters or characters outside the permitted character set (RSKC), such as umlauts. Changing the flag on a characteristic already used by a provider that holds data is accepted; a load that failed activation on such a value can then simply be activated again.",
+  "type": "boolean"
+}
  2. First observedv0.7.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it does so well: it explicitly discloses that supplying attributes replaces the entire list, that an empty array removes all attributes, that omitting them leaves the list untouched, and that the operation internally performs lock → GET → PUT → activate → unlock. This gives the agent a strong mental model of a mutating, potentially destructive operation.

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 compact yet information-dense: two sentences cover scope, destructive replacement behavior, KYF support, and the internal call sequence. Every clause earns its place and key caveats are front-loaded.

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 complex mutation tool with no output schema and no annotations, the description covers the essential operational context: what can be updated, how attribute replacement works, and the internal sequence. It does not describe return values or failure behavior, which is a minor gap given the schema already thoroughly documents parameters.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds helpful context around attributes (replace vs omit) and KYF applicability, but most parameter-level meaning is already present in the schema. It does not substantially enrich individual parameter semantics beyond what the schema provides.

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 names a specific verb ('Update') and a specific resource ('InfoObject'), and immediately enumerates what can be changed: description, lower-case flag, attributes, and KYF fixed unit/currency. This clearly distinguishes it from sibling tools like bw_get_infoobject, bw_create_infoobject, and bw_update_infosource.

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 clear context for when to use the tool: updating a Characteristic InfoObject or a Key Figure's fixed unit/currency, and it explains how to behave when attributes are supplied vs omitted. It does not explicitly name alternative tools for related operations, but the use case is clear enough.

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