Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bw_get_request

Retrieve the full status of one BW load request in a single call: request header, DTP timing, process chain steps, and error messages. Read-only; feed in the request TSN.

Instructions

Full status analysis of one load request in a single call, bundling the request header, DTP information (including start, finish and duration), the process step chain and the message log, errors with their long text. Read-only. For a DTP request that did not finish green, the messages of its data packages are added from the step log of the process chain run that executed it — with message variables and the program location of a runtime error. A request run outside a process chain has no such log, and the output says so. The request TSN comes from bw_list_requests output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format. "text" (default): readable summary. "raw": full parsed JSON of all four payloads, plus the process chain step log where one is read.
storageNoStorage area code (default "AQ"). Take it from the "Storage" line of the bw_list_requests output — the code differs by target type (e.g. AQ inbound, AT/AX active data aDSO, ATTE active text table InfoObject). A wrong code 404s the header/DTP/process sections, but the message log is still returned.
request_tsnYesInternal request TSN from bw_list_requests output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedInput schema / properties / format / description
      Previous value: -"Output format. \"text\" (default): readable summary. \"raw\": full parsed JSON of all four payloads."New value: +"Output format. \"text\" (default): readable summary. \"raw\": full parsed JSON of all four payloads, plus the process chain step log where one is read."
  2. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / storage / description
      Previous value: -"Storage area code (default \"AQ\")."New value: +"Storage area code (default \"AQ\"). Take it from the \"Storage\" line of the bw_list_requests output — the code differs by target type (e.g. AQ inbound, AT/AX active data aDSO, ATTE active text table InfoObject). A wrong code 404s the header/DTP/process sections, but the message log is still returned."
  3. Addedv0.9.1

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 burden and does well: it declares 'Read-only' and discloses the conditional behavior that a request run outside a process chain has no log and the output states so, plus that error messages include long text and runtime-error location. It omits auth/permission requirements and any rate/volume caveats, so not fully exhaustive.

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?

Front-loads the core purpose ('Full status analysis of one load request in a single call') before the enumeration of payloads. Dense but each sentence adds information; the 'Read-only' and process-chain edge case earn their place. Slightly over-packed but not padded.

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?

There is no output schema, and the description compensates by enumerating the four payloads returned and describing the conditional step-log addition, which is the key thing an agent must anticipate. Missing details on the error/404 path are covered in the schema, so the description is nearly sufficient for correct invocation.

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 request_tsn, storage, and format in detail. The description only echoes the TSN provenance already present in the schema and adds no syntax or defaulting guidance beyond it, 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?

States a specific verb (get) and resource (one load request) and enumerates exactly what the response bundles: header, DTP info, process step chain, message log, and error long texts. An agent can distinguish it from bw_list_requests (which only supplies the TSN) without opening either schema.

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?

Gives a clear prerequisite: 'The request TSN comes from bw_list_requests output,' telling the agent which sibling precedes this call. It also frames the scenario where the extra step-log data appears (a DTP request that did not finish green), but names no explicit exclusion against near neighbors like bw_get_dtp or bw_get_process_chain_run_detail.

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