The travel assistant is not only supposed to talk. It is supposed to read the status of a booking, search the travel terms and, if a person agrees, cancel a booking. For that the Agent Service has tools: functions of your own application, web APIs, MCP servers, search and toolboxes. The lesson chooses one kind per requirement and shows schemas (the exam says "tool schemas").
Prior knowledge. How a model chooses a tool, how tools are described, why you start read-only and how errors are returned is taught by "AI track, lesson T7.2"; approvals by "T7.3"; MCP server and client by "T8.1" and "T8.2", permissions for tools by "T8.3"; foreign text as data by "T6.2". The agent and its versions are built in lesson 2.3, the search in lesson 2.2.
The requirement
All numbers are assumptions of the exercise.
| No. | Requirement | Type | Measure | Weight | Source |
|---|---|---|---|---|---|
| 2.4-01 | The agent reads the status of a booking from the booking system. | F | 1 read call per question | Must | Business unit |
| 2.4-02 | The agent searches the travel terms. | F | Lesson 2.2 | Must | Business unit |
| 2.4-03 | A cancellation happens only after a person agrees. | R | 0 cancellations without approval | Must | R-02 |
| 2.4-04 | The tools of reiseassistent and pruefer (E-03) are maintained once. |
Q | 1 place for the list | Should | Operations |
| 2.4-05 | Descriptions and results of tools count as untrusted. | R | Outputs fenced off (R-11) | Must | Security |
| 2.4-06 | Receipts (R-04) are read out as a document. | F | Lesson 5.4 | Could | E-07 |