What the documents look like
On-demand retail store fulfillment processes online orders by the minute, which separates its workload from periodic stocktaking. The materials handled on this page are the instant order, the picking list, the out-of-stock report, and the delivery exception form; these serve as the objects to be checked during contract and transaction material comparison. Because the materials update at minute-level, per order, a comparison conclusion applies only to the current order's material state and does not extend to other orders. The typical operating parties are the supermarket home-delivery store, rider dispatch, and pickers. Each party holds materials with different fields, so a comparison must first confirm that the parties match.
A hypothetical drill sample is used below. The source material for checking consists of three sentences. Sentence one: "Store A generated instant order D-0412-17 at 10:05 on April 12, containing two units of 500 ml ambient milk." Sentence two: "Picking list P-0412-17 records that one unit of ambient milk was picked for the same order, and out-of-stock report B-0412-17 records that the other unit was out of stock." Sentence three: "Delivery exception form E-0412-17 was submitted by the rider at 10:40, with status pending store confirmation." The draft sentence to be judged is: "Order D-0412-17 has completed delivery of two units of ambient milk, and the out-of-stock report has been closed." This draft sentence concerns party Store A, object order D-0412-17, and the states of completed delivery and closed out-of-stock report. The source material shows only one unit picked, one unit out of stock, and an exception form pending confirmation; it does not state that the out-of-stock report was closed or that delivery of two units was completed.
Constraints at the tool calls step
The tool call node decides whether to invoke a tool based on the tool introduction, the parameter introduction, and whether a parameter is required. For plugins, tool parameters are a configurable item; for system modules, tool parameters are already fixed. When a suitable required parameter is absent, the model may not call the tool, so interaction must guide the user to supply the parameter, and the actual request sent must be checked. In advanced orchestration, connecting available tools to the tool call module allows the introduction to be edited to adjust call timing; the documentation recommends tuning a small number of tools first. The tool call termination node, attached after a tool, forcibly ends this tool call, does not call other tools, and does not call the AI to summarize tool results. Retrieval results and similarity scores do not carry permission or entity isolation duties, and retrieval itself does not constitute authorization.
For this page's task, the relevant constraints are that the four material types must fall within the tool introduction's stated input range, that the order number must be treated as a required plugin parameter, that only a small number of tools serving contract and transaction material comparison should be connected, and that the termination node should follow the comparison tool. A missing order number is a missing required parameter, not a permission conclusion. A retrieval hit returns material; it does not confirm the state written in the draft sentence.
Configuration and implementation checks
The table below lists only officially documented settings or implementation checks relevant to this page's main task. The values in the middle column are hypothetical starting points for this drill, not official defaults.
| Configuration item | Hypothetical drill starting point | Check method |
|---|---|---|
| Tool introduction | State that the input conditions are the four material types: instant order, picking list, out-of-stock report, delivery exception form | Compare whether the source material falls within the input range described in the introduction |
| Tool parameters | Set the order number as a required parameter in the plugin parameters | Observe whether the model calls the tool when the order number is absent, and check the actual request |
| Tool connection | Connect only the small number of tools relevant to this page's main task | Inspect whether every connected tool serves contract and transaction material comparison |
| Tool call termination | Attach the termination node after the comparison tool | Observe whether this call ends and no other tool is called |
| Custom tool variable | Add a parameter description for a node not treated as a tool parameter | Check whether that node is called and what workflow follows it |
The hypothetical drill starting point of a small number of tools is chosen because the documentation advises against adding too many tools at once; the comparison object is the call situation when no other tools are connected.
Three common errors
- Treating a retrieval hit as an authorization conclusion. The input is the retrieval result for order D-0412-17; the comparison object is the state field in the source material; the observable result is that retrieval returned material, but the source material does not state that the out-of-stock report was closed, so the closed state in the draft sentence is not supported.
- Treating pending confirmation as completed. The input is delivery exception form E-0412-17; the comparison object is the status field "pending store confirmation"; the observable result is that this status does not equal completed delivery, so the completed-delivery conclusion in the draft sentence lacks a basis.
- Treating a parameter introduction as a guarantee of execution. The input is the order number parameter introduction; the comparison object is the actual request sent; the observable result is that the introduction text does not produce a call, so the request must be checked for whether the order number was actually included.
How to verify the setup
- Input the three source sentences and the draft sentence from the hypothetical sample; compare "two units delivered and completed" in the draft sentence with "one unit picked, one unit out of stock" in the source material. If the source does not state delivery of the second unit, that expression is not supported and is recorded as pending verification.
- Input the status "pending store confirmation" from delivery exception form E-0412-17; compare it with "the out-of-stock report has been closed" in the draft sentence. If the material does not state a closing action, that conclusion lacks a basis, and the evidence gap is retained.
- Input the plugin configuration in which the order number is a required parameter; compare whether the actual request contains that number. If the request lacks the number and the model did not call the tool, record this as a non-call caused by a missing parameter, and do not infer other failure causes.
These checks describe expected observations only. No test, deployment, approval, refund, or other business action is claimed to have occurred. Where the source material is silent, the gap remains a gap.