-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Revise sampling specification to define all valid request and response fields #531
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?
Revise sampling specification to define all valid request and response fields #531
Conversation
f54bdf9 to
93603e9
Compare
|
@dsp-ant or @cliffhall, maybe? This doesn't make any schema changes to the spec, it just fills in missing documentation. |
cliffhall
left a comment
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.
LGTM! 👍
|
Updated, re-requested reviews. |
cliffhall
left a comment
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.
LGTM! 👍
6316ff7 to
9f681bc
Compare
Co-authored-by: Cliff Hall <cliff@futurescale.com>
2f31999 to
dc634be
Compare
|
This is actually quite good but sampling now has changed. Is this worthwhile fixing up and merging? |
|
@LucaButBoring do you have a sponsor for this yet? |
|
No, but is this SEP-worthy to begin with? It should simply be describing the current definitions of some undocumented sampling fields (if anyone disagrees, we may need to relax the phrasing in a few places). |
|
This is a spec enhancement, but I will defer to @dsp-ant if he wants this broadly reviewed or just merged into the draft. Seems small enough of a change. 😄 |
Updates the sampling specification to explicitly define all request and response fields, so that implementers (and more importantly, MCP application developers) can better understand sampling holistically through its spec, rather than wholly relying on the schema alone.
Motivation and Context
See #503. This change improves the written specification by more accurately describing the current expected request and response behaviors of the server and client, respectively.
How Has This Been Tested?
N/A; validated spec website itself in Mintlify. This PR proposes no schema changes and no behavior changes compared to how clients and servers already behave.
Breaking Changes
None.
Types of changes
Checklist
Additional context
This PR is in flight alongside #198 and #522, and may need to be adjusted accordingly depending on the order in which these three PRs are merged.