Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev

bw_delete_request

Deletes load requests from an InfoProvider, removing their data and request-management entries. Required before switching a DTP from delta to full extraction.

Instructions

Delete load requests from an InfoProvider, removing the data they brought in along with their entry in the request management. This is the precondition BW demands before several follow-up steps — above all switching a DTP from delta to full extraction, which BW refuses while delta requests remain in the target. NOT the same as selective deletion of records by condition, which removes rows but leaves the request. Handles both kinds of request: a load request in the inbound queue is deleted, an activation request is rolled back instead — a rollback also undoes every later activation and removes the load request underneath it. Use all_requests=true with target to clear a provider completely, which is the regular case before an extraction-mode change. Asynchronous: a successful call starts the deletion; confirm with bw_list_requests. Returns which requests were rolled back and which were deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoTarget InfoProvider technical name (e.g. "OBJECT_NAME"). Required with all_requests; optional with request_tsn, where it lets the tool report which further requests a rollback cascade took with it.
storageNoStorage area code the request lives in (default "AQ"). Take it from the "Storage" line of bw_list_requests. AT/AX mark an activation request, which is rolled back rather than deleted; so does every InfoObject storage (ATAT, ATTE, ATHI), since InfoObject loads write straight into active data.
request_tsnNoRequest TSN to delete (from bw_list_requests / bw_run_dtp output). Omit when using all_requests.
target_typeNoTarget object type (default "ADSO").
all_requestsNoDelete every request of target in one run (default false): roll back the activations, then delete what is left in the inbound queue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.1
    • changedInput schema / properties / storage / description
      Previous value: -"Storage area code the request lives in (default \"AQ\"). Take it from the \"Storage\" line of bw_list_requests. AT/AX mark an activation request, which is rolled back rather than deleted."New value: +"Storage area code the request lives in (default \"AQ\"). Take it from the \"Storage\" line of bw_list_requests. AT/AX mark an activation request, which is rolled back rather than deleted; so does every InfoObject storage (ATAT, ATTE, ATHI), since InfoObject loads write straight into active data."
  2. Addedv1.5.0

TDQS

A4.9/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 behavioral burden and does so well: it discloses that load requests are deleted, activation requests are rolled back with a cascade that undoes later activations, the call is asynchronous, and the return identifies rolled-back vs. deleted requests. Authorization details are absent, but the destructive and irreversible nature is clear from 'delete' and 'removing the data'.

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 front-loaded with purpose and sibling distinction, then moves through behavior, usage, async confirmation, and return values. Every sentence carries decision-relevant information, and the length is justified by the tool's destructive, multi-mode complexity.

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

Completeness5/5

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

Given no annotations and no output schema, the description is complete: it covers purpose, when to use it, alternatives, both request-type behaviors, asynchronous confirmation, and what the call returns. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3 even without additional parameter detail. The description adds usage context for all_requests=true with target, clarifying the common extraction-mode-change scenario, but most individual parameter meanings are already fully documented in the schema.

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 specific verb and resource: delete load requests from an InfoProvider, including removal of data and request-management entries. It explicitly distinguishes itself from selective record deletion and clarifies how load vs. activation requests are handled, giving the agent a precise mental model.

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?

It states the primary use case (precondition for switching a DTP from delta to full extraction), the regular case for all_requests=true with target, and the exclusion (not selective deletion of records by condition). It also directs the agent to bw_list_requests for asynchronous confirmation.

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