bw-modeling-mcp

bw_update_query_cells

Manage cell definitions in a two-structure BW Query by adding, updating, or removing reference, formula, and help cells at member intersections. All changes are applied in a single save.

Instructions

Manage the cell definitions of an existing BW Query that has two structures (one on each axis): add reference cells (make the value at an intersection of a member of each structure addressable), add formula cells at an intersection, add help cells (formula or selection cells outside the grid, used as reusable operands such as a unit-free denominator), change a cell's formula, description, decimals or scaling, and remove cells. Members and cells are addressed by description or id; bw_get_query lists the existing cells with the member descriptions they sit on. All operations are applied in a single save.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query_name": "<query_name>",
      "operations": "<operations>"
    },
    "name": "bw_update_query_cells"
  }
}

Input Schema

Name	Required	Description
`transport`	No	Transport request number (e.g. DEVK900123). Only needed when the query lives on a transportable package; omit for $TMP queries.
`operations`	Yes	Cell changes, applied in order in one save cycle. A later operation can reference a cell an earlier one added, by its description.
`query_name`	Yes	Technical name of the query to modify (e.g. "QUERY_NAME").

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.1Oct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that all operations apply in one save, that remove_cell is refused while another formula references the cell, and that a reference cell is auto-created when an intersection lacks one. It omits any mention of permissions/locking or error behavior, keeping it below 5.

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?

It is a single dense paragraph, front-loaded with the core purpose and operations, and every clause is informative. Some operation enumeration and cross-references are lengthy, but there is little waste.

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 annotations and no output schema, the description covers the operations, addressing scheme, constraints (reference refusal, auto-creation), and transaction behavior. It is nearly complete, lacking only explicit guidance on sibling choice and error/permission context.

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 schema already documents all parameters thoroughly (operations, formula tree, member addressing). The description adds only marginal param meaning (addressing by description or id, members at any depth), which is the expected baseline when the schema does the heavy lifting.

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 states a precise verb (manage cell definitions) and resource (an existing BW Query with two structures, one per axis), then enumerates the exact operations supported. This clearly distinguishes it from siblings like bw_update_query_key_figures or bw_update_query_layout, which target different query objects.

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 a clear precondition (query must have two structures) and routes the agent to bw_get_query for listing existing cells to reference. It also notes the atomic single-save behavior. It stops short of explicitly stating when to prefer this over sibling update tools, so it isn't a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server