What the documents look like
A brand concession inside a shopping mall accepts unified mall cashiering and deduction-based settlement. The brand ERP and the mall POS each keep a separate sales record, and the monthly reconciliation statement is where those two record paths meet. The joint-operation deduction contract states the deduction ratio and the settlement basis. A mall activity letter changes how costs are borne for a given promotion period. A sales receipt is the original voucher for a single transaction. The supplied brief gives daily and monthly update frequencies, and this page uses only that level of description.
The contract and transaction material comparison task places contract clauses, activity letter conditions, and reconciliation statement figures under the same operating entity, the same period, and the same field before any judgment is made. In concession operations the contract text, the activity letter, and the reconciliation statement often sit with different handlers, so the tool call node is used to select material by context. Authorization status still requires separate verification.
Constraints at the tool calls step
The tool description, the parameter description, and the required flag affect what the model selects. They do not ensure that a call happens or that execution succeeds. System module parameters are fixed, while plugin parameters are configurable. When a tool has no required parameters and the context lacks a suitable value, the model may still call the tool and fabricate a parameter on its own. When a tool has a required parameter and the context holds no suitable value, the model may decline to call the tool, and interaction can be used to guide the user into supplying the parameter.
A tool call termination node attached after a given tool forces the current call to end. It does not call other tools, and it does not call the AI to summarize the tool result. A custom tool variable can extend the variable input for a node that is not treated as a tool parameter or cannot be called as a tool; filling in the matching parameter description lets the tool call reach that node and the workflow after it. In advanced orchestration, connect the available tools to the tool call module, and tune a small number of tools first.
Hypothetical paper exercise. A brand concession and a shopping mall sign a joint-operation deduction contract. The contract text states: "The concession's sales for the month are subject to a twenty percent deduction, and settlement uses the mall POS aggregate as the basis." A mall activity letter states: "During the activity period (March 1 to March 31), the deduction for this concession is temporarily adjusted to fifteen percent." The monthly reconciliation statement states: "Settlement period: March; sales aggregate: a stated RMB amount; deduction ratio: twenty percent." One draft sentence awaiting judgment reads: "The March reconciliation statement deduction ratio matches the temporary activity letter ratio, so settlement can be confirmed directly." That sentence does not state whether the mall confirmed execution of the activity letter, and it does not state whether the reconciliation statement has entered a review process.
The following is a hypothetical custom comparison plugin plan. It was not executed, and the parameters must be checked separately against the actual plugin contract. The intended tool description reads "read the joint-operation deduction contract, mall activity letter, and monthly reconciliation statement text," and states "do not call when the material entity, period, or field is incomplete." Among the plugin parameters, the material type is set as a required parameter limited to the three values contract, activity letter, and reconciliation statement; the comparison field is set as a required parameter. The tool call termination node is attached after the comparison tool so the model does not continue summarizing unconfirmed material. A custom tool variable adds a description for the reconciliation statement review status and points to the manual verification step.
Configuration and implementation checks
| Configuration item | Setting on this page | Basis and verification method |
|---|---|---|
| Tool description | Read contract, activity letter, and reconciliation statement and compare the same field | The description states the purpose and the situations where the tool should not be called; during tuning, observe whether the model selects by material type |
| Material type parameter | Required parameter limited to contract, activity letter, reconciliation statement | When no suitable value exists the model may decline to call; supply it through interaction and check the actual request |
| Comparison field parameter | Required parameter covering entity, period, and field name | The parameter description explains the meaning of the value; the parameter description is not treated as an execution assurance |
| Tool connection | Connect the above tools to the tool call module | After connecting in advanced orchestration, edit the description and tune a small number of tools first |
| Tool call termination | Attached after the comparison tool | The termination node ends the current call and does not call the AI to summarize the tool result |
| Custom tool variable | Add a description for the reconciliation statement review status | Adds a variable for a node not treated as a tool parameter, so the call reaches the workflow after that node |
Three common errors
- Treating the temporary ratio in the activity letter as a ratio the reconciliation statement already applied. In the exercise the activity letter states a temporary adjustment to fifteen percent from March 1 to March 31, while the reconciliation statement states a deduction ratio of twenty percent. The two values are mutually exclusive for the same period and the same field, which is a contradiction; the draft sentence calling them consistent does not match that comparison result.
- Treating material that lacks review or execution evidence as directly confirmable for settlement. The exercise provides no review status for the reconciliation statement and no execution record for the activity letter, so the settlement claim remains to be verified. No pending-review or completed status is supplied.
- Treating tool call termination as business termination. The termination node only ends the current tool call and stops AI summarization. It does not change the status of the reconciliation statement in the business system, and it does not mean settlement has been executed.
How to verify the setup
- Input the three source texts from the exercise and the draft sentence, then compare the entity, period, and deduction ratio fields across the contract, activity letter, and reconciliation statement. If the model output states that the activity letter ratio and the reconciliation statement ratio are mutually exclusive for the same period and the same field, and does not claim settlement is confirmed, the expectation is met. If the output calls the two consistent, the expectation is not met.
- Input the reconciliation statement whose review status is not stated in the exercise, and compare the draft sentence "settlement can be confirmed directly" against what the material actually states. If the output records the reconciliation statement status as pending verification or unsupported, the expectation is met. If the output states that review is complete, the expectation is not met.
- Input a request in which the material type is missing, with material type set as a required parameter and no suitable value in context. If the model is observed not calling the comparison tool, or requesting the material type through interaction, the expectation is met. If the model fabricates a material type on its own and completes the comparison, the expectation is not met.