How Agent Tool Invocation Works: Synchronous Conversation Loop and Asynchronous Task System

An Alibaba Cloud Developer Community article breaks down the complete chain of an Agent from user input to tool invocation, asynchronous task execution, and feeding results back into the conversation, splitting it into two layers: a synchronous conversation loop and an asynchronous task system. Tools are registered as Spring Beans; duplicate names or duplicate service_type values cause startup to fail outright. The tool table is injected narrowed by the material types visible to the model, and is injected from the same source as the system prompt. The server executes tool invocations serially, with parallel_tool_calls = false by default; long tasks return a recordId immediately after submission, and a worker callback persists and settles the result.