Before and After: Approval-Gated Tool Calls
Design a tool-calling workflow that controls when and how many external actions can run.
The facilities bot can take real actions. What changes when the team adds approval-gated tool control? Before: all action tools are exposed before approval is known. After: approval check runs first; action tools unlock only after validation. tool_choice forces the approval-check step, so the model cannot skip straight to the action tools. Parallel action calls are disabled around approval, because room access and catering depend on one validation result. The allowed tool subset changes after approval, keeping unavailable actions out of the model's current choice set. Application validation still decides whether the approval token is current before any facilities system…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in