-
Notifications
You must be signed in to change notification settings - Fork 3.5k
DRAFT docs, ch3 - elicitation #335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces a new documentation chapter (3.10) focused on elicitation functionality in MCP (Model Control Protocol) servers. The chapter demonstrates how to implement user preference collection and interactive booking scenarios.
- Adds a Python server implementation showcasing elicitation patterns for booking scenarios
- Creates placeholder TypeScript implementation file
- Establishes new chapter structure in the documentation
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
03-GettingStarted/10-elicitation/code/python/server.py | Complete Python MCP server demonstrating elicitation with booking preferences |
03-GettingStarted/10-elicitation/code/typescript/src/index.ts | Placeholder TypeScript file with basic comment |
03-GettingStarted/10-elicitation/README.md | Basic chapter title for the elicitation documentation |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
@@ -0,0 +1 @@ | |||
// server for elicitation No newline at end of file |
Copilot
AI
Aug 18, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The TypeScript implementation is incomplete with only a comment. This placeholder should either contain actual implementation code or a more descriptive comment explaining the intended functionality.
Copilot uses AI. Check for mistakes.
Co-authored-by: Copilot <[email protected]>
@softchris can you fix the suggestions provided |
Purpose
Elicitation is about supporting a scenario where the user makes a first selection, for example a booking, and it's not available. The elicitation happens when the server asks the user to make a different choice and "elicits" a new response from the client.
Does this introduce a breaking change?
When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.
Does this require changes to learn.microsoft.com docs or modules?
which includes deployment, settings and usage instructions.
Type of change