@findleyr, please note - this changes currently do not work with MCP Inspector 0.17.0, as modelcontextprotocol/modelcontextprotocol#1531 is not implemented yet. I have created issue modelcontextprotocol/inspector#861 to track this.

@findleyr, please note - this changes currently do not work with MCP Inspector 0.17.0, as modelcontextprotocol/modelcontextprotocol#1531 is not implemented yet. I have created issue modelcontextprotocol/inspector#861 to track this.

Ah, this is a really important point. We need to not return this data based on the client's protocol version!
This definitely warrants a test!

Thanks for this change!

Can you add a basic smoke test (perhaps just adding to TestEndToEnd) that verifies the client receives the new metadata correctly?

(I'm sure it works, but good to have at least one end-to-end test).

Yes, was about to ask, if we are good with this changes. I will add tests accordingly.

I have updated E2E tests. And updated streamable tests - which were using shared object.

We need to not return this data based on the client's protocol version!

As of now, Inspector integration fails, as specification draft has changed after original changes were incorporated in inspector. I am not sure, if this would still be a braking change for clients implementing '2025-06-18' or earlier protocol.

@findleyr if we have to omit this info from server, could you please suggest, how we should go about it? Considering we may have to implement similar checks for future specs as well.