A bad MCP elicitation schema now shows a clear error instead of a misleading reconnect message.
What's wrong with this entry?
A malformed requestedSchema in an MCP elicitation now produces an InvalidParams error naming the constraint, rather than a misleading reconnect message.
- parse failure on
requestedSchemais converted into an MCP InvalidParams error explaining the constraint - the completion notification handler is registered against the literal method name
notifications/elicitation/complete
notifications/elicitation/complete
Strings lifted out of the shipped bundle, so the claim above can be checked against them.