Inna Harper

> Thanks @ihrpr , > > 1. I had the requestSchema implemented locally, then punted it hoping [RFC: add tool `outputSchema` and `DataContent` type to support structured content #356](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/356) will...

> > Thanks @ihrpr , > > > > 1. I had the requestSchema implemented locally, then punted it hoping [RFC: add tool `outputSchema` and `DataContent` type to support structured...

> Thanks @ihrpr , that confirms, and to get your opinion on content in result, it could be an open ended field. Like you have described, I agree its simpler,...

> Also, this seems to assume support for Server-Side Events, but I think that's optional in the spec generally. I've been thinking of ways to support this type of thing...

https://github.com/modelcontextprotocol/python-sdk/pull/625 - here is prototype for elicitation in Python SDK

> But, regardless, my point was about the elicitation bubbling up through layers of agents. How would that work with the sampling-derived proposal in this PR? [Here is an example...

> How will the elicitation be forwarded? Will it require maintaining a long-running open connection? What requirements will it place on servers and clients? In that case, the "Personal Assistant"...

Thank you for this contribution. While dynamic tool enabling/disabling could be useful for testing, we're closing this PR because: 1. It creates API confusion (disabled vs non-existent tools) 2. Requires...

> Added the ability to dynamically enable and disable tools at runtime with client notifications. Please can you expand on this? The Typescript Feature mentioned is for [Dynamic Servers](https://github.com/modelcontextprotocol/typescript-sdk/pull/247), is...

thank you for reporting this! Updated the example in readme