Skip to content

Conversation

@stephentoub
Copy link
Contributor

Enhanced InvokeCoreAsync in McpClientTool.cs to handle non-text content by converting it to AIContent when possible. This enables richer content handling for downstream IChatClients while maintaining fallback serialization for unsupported cases.

Enhanced `InvokeCoreAsync` in `McpClientTool.cs` to handle non-text content by converting it to `AIContent` when possible.  This enables richer content handling for downstream `IChatClients` while maintaining fallback serialization for
unsupported cases.
@PederHP
Copy link
Member

PederHP commented Nov 4, 2025

Ah, this looks great for IChatClients with media tool result support.

The tests made me think that ResourceLinks could be handled similar to how vs code does.

Afaik it resolves those in a way where the message history retains that it's a link, and then it fetches the resource from the mcp server when needed, ie after tool call and on reconnect/resume.

It's tangential to this PR I know, but having a resource link AIContent with an McpClient reference and dynamic resolution would replicate this I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants