A reporting tool's result must include a rendered chart, a short written summary, and a pointer to a full report that the client can fetch later without the report's contents being placed inline. Which combination of unstructured content types fits this result?
Select an answer to reveal the explanation.
Short Explanation
A tool result is like a mixed tray: you can serve a picture, some words and a link side by side. The resource_link is your 'fetch it later' pointer, while an embedded resource ships the whole thing inline. Watch for that difference.
Full Explanation
Unstructured tool results live in the content array, which can hold multiple items of different types: text, image, audio, resource_link and embedded resource. Image content carries base64 data with a MIME type, text content carries the written summary, and a resource_link carries a URI, name and optional MIME type so the client can fetch or subscribe to the resource later without the contents being inlined. That combination matches every requirement in the scenario. An embedded resource places the resource contents directly in the result, which contradicts the requirement to keep the report out of the payload; it is the right choice only when the content should travel inline. A single text block misstates the rules, since the content array explicitly supports several items of different types in one result. Audio content is for audio data, not charts, and a prompt message is a construct returned by prompts/get, not a content type for tool results. Exam caveat: resource links returned by tools are not guaranteed to appear in the server's resources/list results, so clients should not assume that they will. Operational check: inspect the tool result and confirm it contains one image item with a valid MIME type, one text item, and one resource_link item whose URI the client can read.