{"version":"2.1.221","anchor":"mcp-elicitation-schemas-are-validated-with-a-clear-error","canonical_anchor":"mcp-elicitation-schemas-are-validated-with-a-clear-error","heading":"MCP elicitation schemas are validated with a clear error","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-elicitation-schemas-are-validated-with-a-clear-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP elicitation schemas are validated with a clear error\n\nA bad MCP elicitation schema now shows a clear error instead of a misleading reconnect message.\n\n**What**\n\nA malformed `requestedSchema` in an MCP elicitation now produces an InvalidParams error naming the constraint, rather than a misleading reconnect message.\n\n**Details**\n\n- parse failure on `requestedSchema` is converted into an MCP InvalidParams error explaining the constraint\n- the completion notification handler is registered against the literal method name `notifications\/elicitation\/complete`\n\n**Evidence**\n\n`notifications\/elicitation\/complete`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}