Skip to main content
Glama
Sign In
bw-modeling-mcp

bw-modeling-mcp

by dnic-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_update_query_exceptions

Add, update, or remove exceptions with alert-level thresholds that color data cells in an existing BW query; all operations apply in one save.

Instructions

Manage the exceptions (alert levels that colour data cells) of an existing BW Query: add exceptions with thresholds per alert level, change them, and remove them. An exception is evaluated on the data cells of one member per structure or on all elements of a structure, and can colour the evaluated cell or other cells. Members and exceptions are addressed by description or id; bw_get_query lists the existing exceptions. for_each_member creates the same exception once per listed member. 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_exceptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
transportNoTransport request number (e.g. DEVK900123). Only needed when the query lives on a transportable package; omit for $TMP queries.
operationsYesException changes, applied in order in one save cycle.
query_nameYesTechnical name of the query to modify (e.g. "QUERY_NAME").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: all operations are applied in a single save (implying one atomic commit), how an exception is evaluated on members, and that for_each_member fans out one exception per member. It does not cover permissions, required query state (e.g. inactive/unlocked), or failure behavior, which keeps it below a 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?

Five tight sentences front-load the purpose, then layer evaluation semantics, addressing convention, sibling lookup, fan-out, and save behavior. There is no filler, though the middle sentences are dense run-ons that could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description covers evaluation and commit semantics well but omits prerequisites such as whether the query must be inactive and what a failed batch returns. The transport requirement is left entirely to the schema.

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 query_name, transport, and every operation field including thresholds and for_each_member. The description adds only the general addressing convention (description or id) and largely restates the for_each_member fan-out already present in the schema, so baseline 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 names the verb set (add, change, remove) and the exact resource (exceptions, defined parenthetically as alert levels that colour data cells) of an existing BW Query. This clearly distinguishes it from siblings such as bw_update_query_cells, bw_update_query_filter, and bw_update_query_layout.

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 tells the agent to consult bw_get_query to list existing exceptions before updating or removing, which is real routing guidance, and it clarifies that members and exceptions are addressed by description or id. It stops short of stating when not to use it or contrasting with the other bw_update_query_* tools.

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