Skip to content

Conversation

@LucaButBoring
Copy link
Contributor

@LucaButBoring LucaButBoring commented May 15, 2025

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

  • 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

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.

@LucaButBoring LucaButBoring force-pushed the spec/sampling-includecontext branch from f54bdf9 to 93603e9 Compare May 15, 2025 17:14
@LucaButBoring
Copy link
Contributor Author

@dsp-ant or @cliffhall, maybe? This doesn't make any schema changes to the spec, it just fills in missing documentation.

cliffhall
cliffhall previously approved these changes Jul 1, 2025
Copy link
Member

@cliffhall cliffhall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍

@cliffhall cliffhall requested a review from evalstate July 15, 2025 16:39
@LucaButBoring
Copy link
Contributor Author

Updated, re-requested reviews.

@LucaButBoring LucaButBoring requested a review from a team July 16, 2025 20:10
@LucaButBoring LucaButBoring requested a review from cliffhall July 16, 2025 21:41
cliffhall
cliffhall previously approved these changes Jul 16, 2025
Copy link
Member

@cliffhall cliffhall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍

@LucaButBoring LucaButBoring force-pushed the spec/sampling-includecontext branch from 2f31999 to dc634be Compare August 13, 2025 18:49
@dsp-ant
Copy link
Member

dsp-ant commented Nov 21, 2025

This is actually quite good but sampling now has changed. Is this worthwhile fixing up and merging?

@cliffhall cliffhall requested review from a team as code owners November 21, 2025 19:37
@LucaButBoring
Copy link
Contributor Author

@dsp-ant Updated to reflect #1577

@localden localden added the SEP label Dec 5, 2025
@localden
Copy link
Contributor

localden commented Dec 5, 2025

@LucaButBoring do you have a sponsor for this yet?

@LucaButBoring
Copy link
Contributor Author

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).

@localden
Copy link
Contributor

localden commented Dec 5, 2025

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. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants