bhosmer-ant

> Having `outputSchema` restrict you to to returning a single text content entry who's `text` validates to the schema feels oddly restrictive. That approach makes annotations largely pointless, and I...

> A couple of comments on this as I prepare to undraft #223 for RFC: > > * I've updated [RFC: Client / Server Content capabilities #223](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/223) to indicate that...

> It's still not clear to me how this is better than the additional 3-4 lines of code required to achieve this with the current spec here : https://gist.github.com/evalstate/e49cb163297c1ab940fb8a98e31947ed -...

@ihrpr fyi new rev makes `structuredContent` an object, and updates the docs w/compatibility language (and a better example). ([TS SDK example](https://github.com/modelcontextprotocol/typescript-sdk/pull/454) updated too)

@lukaswelinder hey, so here's my attempt to summarize the differences between this proposal and #371. TLDR I think they've got two different categories of use case in mind, but AFAICT...

> > * there's no way to constrain a tool to return a single DataContent block, since outputSchema applies to per-block rather than a per-result. > > I sort of...

> I don't recall where it was brought up, but we may consider a broader approach to dictating the tool's output. Something like this: > > ```ts > interface Tool...

@evalstate first of all, thanks for your patience with the sprawly discourse on #356 :) A few general questions/observations here, and then I'll follow up on #356 with some questions...

> > ... > > _Embedded_ simply means a Resource contained within a CallToolResult or PromptMessage. It doesn't have special meaning beyond that. > > > ... > > We...

@evalstate thanks for the quick turnaround! If you could fix merge conflicts then it's button-pushing time