shaun smith

> I've been following the suggestions in some detail, perhaps I'm missing some nuance here but the simplest solution to me seems to be. > > 1/ Add output Schema...

> Using TextContent for JSON is a common hack (employed by myself and many others) The appropriate type to use for JSON is `TextResourceContent` with a mimeType of `application/json`, but...

> > Using TextContent for JSON is a common hack (employed by myself and many others) > > The appropriate type to use for JSON is TextResourceContent with a mimeType...

@Ejb503 - `CallToolResult` already supports `EmbeddedResource` which allows you to return mimeType specified text, _with_ annotations indicating whether it should be for the Assistant or the User. > I believe...

I've just updated #223 to remove `generates` from `ServerCapabilities` and to a `generatesHint` Tool Annotation. It seems that would be quite a good place to add something like a `schemaRef`...

This looks like a reasonable convention. I know this RFC deliberately and sensibly sidesteps ownership of the "@" namespace, but there may need to be some connection to the registry...

Hi @josephbharrison - thanks for raising this topic (and I can't wait to try the code in that repo -- thank you for taking the initiative to do that --...

I've read the thread a couple of times, but I want to make sure I understand what is being proposed @yinzara . It sounds like your idea is to refactor...

> < There is no equivalent for "Output Schema" - the Host application needs to decide whether or how to pass that to the model as an additional String somewhere...

Great question - I'd propose it remain mandatory for the following reasons: - The type used in `CallToolResult` and `PromptMessage` inherits from `ResourceContents` which is also used for `ReadResourceResult` which...