Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_create_infoobject

Create inactive SAP BW InfoObjects (characteristics or key figures) with specified properties; use a separate activation call to make them active.

Instructions

Create a new InfoObject — Characteristic (CHA) or Key Figure (KYF) — inactive. Sequence: lock → POST create → unlock. After creation call bw_activate with object_type "iobj" to activate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInfoObject name, max 9 characters (e.g. "IOBJ_NAME").
lengthNoCHA only. Field length. Default 10.
packageNoDevelopment package. Default "$TMP".
data_typeNoCHA only. ABAP data type. Default "CHAR".
info_areaYesInfoArea to assign the InfoObject to (e.g. "NEXTJUICE").
transportNoTransport request number (e.g. DEVK900123). Only required if the BW system requires transport assignment.
fixed_unitNoFixed unit of measure for QUAN key figures (e.g. "KWH", "M3"). Required when object_specific_data_type is QUAN.
lower_caseNoCHA only. Allow lower case letters (RSDCHABAS-LOWERCASE). Default false. Set true for characteristics whose values may contain lower case letters or characters outside the permitted character set (RSKC), such as umlauts — the flag switches off that check for this characteristic. Without it, a load carrying such values is accepted but fails later during request activation.
with_textsNoCHA only. Generate text tables. Default false.
descriptionYesShort and long description text.
fixed_currencyNoFixed currency for CURR key figures (e.g. "EUR"). Required when object_specific_data_type is CURR.
infoobject_typeNoInfoObject type: CHA (Characteristic) or KYF (Key Figure). Default "CHA".
aggregation_typeNoKYF only. Aggregation type. Default "SUM".
with_master_dataNoCHA only. Generate master data tables. Default false.
conversion_routineNoCHA only. Conversion routine (e.g. "ALPHA"). Default "ALPHA" for CHAR/NUMC, "" for others.
compound_infoobjectsNoTechnical names of the compound parent InfoObjects, in order. CHA only. Example: ["COMPND_IOBJ_NAME"].
referenced_infoobjectNoCHA only. Reference to an existing InfoObject (e.g. "IOBJ_NAME"). Omit withMasterData/withTexts — they are inherited. Default "".
object_specific_data_typeNoKYF only. Data type. Default "DEC". keyfigureType and semantics are derived automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • addedInput schema / properties / lower_case
      Added value: +{
+  "description": "CHA only. Allow lower case letters (RSDCHABAS-LOWERCASE). Default false. Set true for characteristics whose values may contain lower case letters or characters outside the permitted character set (RSKC), such as umlauts — the flag switches off that check for this characteristic. Without it, a load carrying such values is accepted but fails later during request activation.",
+  "type": "boolean"
+}
  2. First observedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the critical behavior that the object is created inactive and must be activated via bw_activate. It also mentions the lock/unlock sequence, which are important side-effects. This is above average disclosure for a tool with no annotations.

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?

Two sentences with zero fluff. The first states the purpose, the second gives the essential workflow. All information is relevant and 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 tool with 18 parameters and no output schema, the description covers the critical lifecycle (creation is inactive, activation needed) and the locking sequence. The schema covers parameters exhaustively. It doesn't mention error cases or prerequisites, but those are minor given the rich schema and workflow disclosure.

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?

The input schema has 100% coverage, with each parameter described including defaults, type-specific constraints (e.g., 'CHA only'), and examples. The tool description adds no parameter-specific information, so the baseline of 3 applies.

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 explicitly states 'Create a new InfoObject' and specifies the two types (CHA or KYF), which is a clear verb+resource. It also distinguishes this from update tools by noting it creates an inactive object, making the purpose unambiguous.

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?

It gives explicit operational guidance: the sequence 'lock → POST create → unlock' and instructs to call bw_activate after creation. This tells the agent exactly when and how to use the tool. It doesn't explicitly mention alternatives (e.g., bw_update_infoobject), but the create vs update distinction is clear from context.

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