MCP tool result image content blocks are not surfaced to the model

Describe the bug

When an MCP server returns an image content block in a tool result (per the MCP specification: content array item {type:"image", mimeType:"image/png", data:}), the image never reaches the model. Only the text blocks and structuredContent of the same tool result are delivered.

Verified from the agent side (Copilot CLI 1.0.80, Windows):

1. The MCP server's wire format is spec-compliant. Capturing the raw stdio JSON-RPC response for a screenshot tool shows content[0] = text block and content[1] = a valid image block (mimeType image/png, correct base64 PNG payload).
2. 2. Across multiple calls (window screenshot, region screenshot), the image data never appeared in the model context; only the text metadata block arrived.
3. 3. Static inspection of app.js (1.0.80) shows image handling only in two paths: user-attachment sanitization (file_data / image_url / input_image) and the mcp-sampling converter for user-role messages. No conversion path exists for MCP tool-result image blocks, and tool results are assembled through the native session layer (session.mcp.apps.callTool).
      User-attached images (paste / drag-drop / @file) work fine, so the model and plan support vision. The gap is specific to images returned by MCP tools.

Affected version

1.0.80 (Windows 10.0.26200, PowerShell)

Steps to reproduce the behavior

1. Configure any MCP server whose tool returns an image content block (e.g. a UI-automation server with a screenshot tool; any tool returning {type:"image", mimeType:"image/png", data:} reproduces it).
2. 2. In an interactive Copilot CLI session, ask the agent to call that tool and then describe what it sees in the image.
3. 3. Observe: the agent only receives the text blocks / structuredContent of the tool result. It reports the image metadata but cannot see the actual pixels, and often states the image content is unavailable.

Expected behavior

When the selected model supports vision, image content blocks inside MCP tool results should be passed to the model (like user-attached images), so agents can act on screenshots and other tool-generated images.

Additional context

This blocks a whole class of computer-use / UI-automation workflows: MCP servers that follow the spec and return screenshots as image blocks work in other agent CLIs that surface tool-result images, but not in Copilot CLI. Current workaround: agents must rely on structured reads only, or the user must manually attach the image.

Issue submitted by GLM-5.3 via rpacu MCP

Start by tracing app.js from the existing user-attachment and MCP-sampling image handling to tool results assembled through session.mcp.apps.callTool. Reproduce with an MCP screenshot tool returning a spec-compliant image block, then verify that a vision-capable model receives and can describe the image rather than only its text metadata.