Skip to main content
Glama
lingcSun

mcp-bw-adt-api

by lingcSun

bw_reporting_update_view

Update BICS axes and refresh the result set by posting the full infoObject state from the initial view to re-render the report.

Instructions

POST updated BICS axes and refresh the result set. Pass the full infoObject state (name/id/axis/pos) from bw_reporting_initial_view. Prefer bw_reporting_preview when you only need to set row/column characteristic names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesFull selection state (all infoObjects with ROWS/COLUMNS/FREE).
toRowNoResult-set end row inclusive (default ~1000 on server).
fromRowNoResult-set start row (default 0).
providerYesProvider name, with or without ! prefix.
outputPathNoIf provided, the full result is written to this path (under the workdir) and the tool returns only a small summary envelope { ok, outputPath, bytes, summary }. Objects/arrays are written as JSON; ONLY the bw_*_get_xml family writes the raw XML string as plain text (that file is directly reusable as xmlPath in a later save call). Other *_get tools (e.g. bw_dtp_get, bw_trfn_get) write the PARSED XML-to-JSON tree, not raw XML — use the matching bw_*_get_xml tool when you need the raw XML string. Use outputPath for large responses (XML, table data, logs, dataflow graphs). When set, tools skip inline pagination/projection so the file contains the complete payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral burden. It does disclose a key behavioral requirement (full state expected, not partial axes) and implies mutation through 'POST' and 'refresh', but it does not disclose side effects, persistence, permissions, or default return behavior.

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 tight sentences with no filler. The core behavior is front-loaded and the sibling routing guidance is delivered economically.

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 five parameters and full schema coverage, the description plus schema is largely sufficient. The missing piece is a clear statement of the default return value without outputPath, although the outputPath parameter description partly compensates.

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%, so the baseline is 3. The description adds important semantic context beyond the schema by specifying that the state array must contain the full infoObject state from bw_reporting_initial_view, which clarifies what 'full selection state' means in practice.

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 action ('POST updated BICS axes and refresh the result set') and the resource, and it explicitly distinguishes itself from bw_reporting_preview. The instruction to pass the full state from bw_reporting_initial_view further clarifies its role in the reporting workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete usage guidance: pass the full infoObject state from bw_reporting_initial_view, and prefer bw_reporting_preview only for row/column characteristic names. This is explicit when-to-use vs alternative routing.

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