Skip to content

docs: clarify subscription completion result - #3171

Merged
dsp-ant merged 2 commits into
modelcontextprotocol:mainfrom
DaleSeo:docs/clarify-subscription-completion
Aug 20, 2026
Merged

dsp-ant merged 2 commits into
modelcontextprotocol:mainfrom
DaleSeo:docs/clarify-subscription-completion

Conversation

@DaleSeo

@DaleSeo DaleSeo commented Jul 29, 2026 •

Copy link
Copy Markdown
Member

Motivation and Context

Right now, the text calls the successful subscriptions/listen response "empty," but the result shown right below it includes resultType and the required subscription metadata. That could be interpreted as requiring a literal result: {} object, which would conflict with the schema and example.

This wording describes it as a completion result instead and clarifies that it contains no method-specific data beyond the standard result fields and subscription metadata.

How Has This Been Tested?

npm run prep

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

@DaleSeo
DaleSeo marked this pull request as ready for review August 2, 2026 23:07
@DaleSeo
DaleSeo requested a review from a team as a code owner August 2, 2026 23:07

@dsp-ant dsp-ant left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

good catch.

@dsp-ant
dsp-ant merged commit cbd5765 into modelcontextprotocol:main Aug 20, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants