The whole thread, both channels merged and serialized for a model to read before drafting. One string: a header with the counterpart identity and link state, the sender profile, the current scenario and attention state, the resolved autonomy ladder, the active plan and the open tasks, then the message tail in chronological order with the timeline events inline.

Use it instead of stitching get_conversation and search_messages together by hand: the budget is applied across messages AND events at once, so what you get back is the most recent coherent slice rather than two lists to merge. result.truncated says the tail was cut; raise max_tokens (500..50000, default 8000) or page the real history with search_messages.

It is what the team's own AI SDR reads, and what an external agent should read before answering a lead. It does not decide anything and writes nothing: drafting and sending are the messages verbs.

Contract:

• MCP tool get_conversation_llm_context, registry package mcp.unibox/conversations, mount unibox.inbox.
• Operation action, response envelope action.
• Flags: read only.