Fix example server elicitation conf

[pbezglasny]

For elicitation request fix checking response schema: { method: z.literal('elicitation/create') } as it is not part of client response.
Similar thing is for sampling tool, but this PR does not change check.

conformance/examples/servers/typescript/everything-server.ts

Lines 311 to 314 in 5c15113

	z
	.object({ method: z.literal('sampling/createMessage') })
	.passthrough() as any
	);

Also a question: test_elicitation always returns success result despite any errors, is it expected? If not I can update the PR.

Motivation and Context

How Has This Been Tested?

Using mcp inspector

Breaking Changes

No

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[Copilot]

Pull Request Overview

This PR enables elicitation support in the example server and fixes the incorrect response schema validation for elicitation requests. The server previously validated client responses with a schema that incorrectly expected a method field, which only exists in requests, not responses.

• Added elicitation: {} capability to server configuration
• Fixed response schema validation for three elicitation tool implementations by replacing the incorrect z.object({ method: z.literal('elicitation/create') }).passthrough() with z.any() as any

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/modelcontextprotocol/conformance/@modelcontextprotocol/conformance@29

commit: fffa835

[pbezglasny]

Hey @felixweinberger could you please check this PR

[pcarleton]

thanks for this @pbezglasny ! the schema was incorrect you're right. I switched it to the actual result rather than any

test_elicitation would probably be good to return an error rather than success, I agree.