shaun smith

I'd prefer this was fixed to `text/plain` if it is going to be added.

Yes, my view is that TextContent should have the guarantee that it is `text/plain`. `TextContent` is by far the most widely used type, and we already have `TextResourceContents` for transmitting...

The current specification supports this workflow: - A "Search" Tool offers search results to the Human, with Prompts/Resources offering completions for UX - A "Use" Tool from provides a `ToolListChangedNotification`...

OK - one more question please... from your description this interaction describes direct Host->Client->Server communication with no LLM intermediary? The issue here is that there are an overwhelming number of...

> this is meant as a tool that LLMs can invoke to search for a tool. i think this is the issue. unless it changes the semantics of what happens...

@LucaButBoring > The host process never needs to call tools/list The specification supports an MCP Server returning a single "search" tool on first use, with a dynamically updating Tool List,...

I initially took a look at the "single word change" to the spec thinking it would be a simple improvement, and enable "initialize free" MCP Server Usage. In practice as...