A developer is building a Foundry Agent Service agent for an e-commerce site. When a shopper asks whether a specific item is currently in stock, the agent must query the live inventory database and return the real quantity at that moment, not a memorized answer. Which capability should the developer configure the agent to use?
Select an answer to reveal the explanation.
Short Explanation
If a shopper needs the actual, right-now count, you give the agent a function or tool that calls the inventory API while the conversation is happening. That hands back the live quantity instead of a remembered, stale, or guessed number.
Full Explanation
The correct capability is a function or tool definition that calls the inventory API and returns its live response to the model. This lets the agent request real-time data during the conversation and return the actual quantity on hand at that exact moment, which is exactly what the shopper is asking about. A retrieval-augmented generation index built from last month's product catalog PDF is incorrect because it is a static snapshot; it can describe what a product is but cannot report a quantity that changes by the hour. Fine-tuning the model on historical stock-level examples is incorrect because it teaches the model patterns from the past, not the current live count, so it would produce a plausible-sounding but potentially wrong number. A longer system message instructing the model to guess reasonable stock levels is incorrect because it produces an invented answer with no connection to the actual database, which is worse than saying nothing, since a shopper acting on a guessed number could be misled into ordering something that is not actually available. Only a live function call reaches outside the model to the authoritative, moment-in-time source of truth.