This is a write up of a design discussion on SEP 2322-MRTR and design decision
Should requests for more information (i.e. the IncompleteResult
response) be supported as a response type on to all ClientRequests, or
should it be limited to a subset of Client Requests?
This is a draft SEP for Multi Round-Trip Requests (MRTR).
## Motivation and Context
See SEP for details.
## How Has This Been Tested?
Not tested yet, that will happen when we implement.
## Breaking Changes
See SEP for details.
## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
## Checklist
- [x] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally
- [x] I have added appropriate error handling
- [x] I have added or updated documentation as needed
## Additional context
N/A
---------
Co-authored-by: Caitie McCaffrey <caitiem20@github.com>
As part of MCP joining the Linux Foundation, this PR updates licensing
to Apache 2.0 for new contributions while grandfathering existing MIT
code. See modelcontextprotocol/modelcontextprotocol#1994
- Change meeting day to Wednesdays at 1pm PT
- Remove antitrust reminder from meeting agenda (policy still applies)
- Remove public notes mention (not currently available)
- Remove Interoperability from focus areas
