Library staff need an agent that searches an internal wiki and can book meeting rooms through an API. Which tool mix is correct?

Library staff need an agent that both searches an internal wiki and books meeting rooms through an API, so the correct tool mix is a search tool over the internal wiki plus a room-booking API tool. Knowledge/search covers procedures and policies; the booking API performs the state-changing action staff actually need. Foundry agents commonly combine retrieval tools with action tools in one staff workflow. A search tool over the internal wiki plus a room-availability API tool only checks whether rooms are free but cannot execute a booking, so staff can read how-to pages and see open slots but still can't finish the reservation in-product. An edit tool for the internal wiki plus a room-booking API tool can place bookings while editing the internal wiki instead of searching its content, so it risks changing procedures and policy pages instead of reading current guidance documented in the wiki. A search tool over the internal wiki plus a room-booking API test tool lets staff read policies and try test bookings but cannot create a real booking, so they can look up guidance and run sandbox calls but still can't reserve a room. On the exam, staff agents mix search/knowledge tools with action APIs; distractors pair search with an availability-only tool, an edit tool instead of wiki search, or pair search with a test-only tool. Caveat: booking tools need authorization scoped to the staff identity—do not expose the same booking privileges to public patron agents. Operational check: ask the staff agent a procedure-plus-booking request, verify wiki search and booking API are both invoked, and confirm bookings appear in the facilities system under the correct staff credentials.