It is worth setting the expectation in the CheatSheet that WebMCP is in early preview, under active development and the API surface is changing frequently as a result of that, otherwise users of the cheatsheet might be surprised when some of the APIs documented there don't work.
It is worth setting the expectation in the CheatSheet that WebMCP is in early preview, under active development and the API surface is changing frequently as a result of that, otherwise users of the cheatsheet might be surprised when some of the APIs documented there don't work.
Noted, will try to make it more clear