Uh oh!
There was an error while loading. Please reload this page.
[v1.x backport] Use correct schema for client sampling validation when tools are present - #1407
Merged
pcarleton merged 1 commit intoJan 20, 2026
Conversation
…sent When a sampling request includes tools or toolChoice, the client now validates the response against CreateMessageResultWithToolsSchema (which supports array content with tool_use blocks) instead of always using CreateMessageResultSchema. This fixes validation failures when client handlers return tool_use content formatted as an array, which was incorrectly rejected with "Invalid input: expected object, received array". Fixesmodelcontextprotocol#1346 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
commit: |
Uh oh!
There was an error while loading. Please reload this page.
sgmakgg added a commit
to boringstudio-org/mcp-gitea
that referenced
this pull request
Mar 13, 2026
…#17) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@modelcontextprotocol/sdk](https://modelcontextprotocol.io) ([source](https://github.com/modelcontextprotocol/typescript-sdk)) | dependencies | patch | [`1.25.2` → `1.25.3`](https://renovatebot.com/diffs/npm/@modelcontextprotocol%2fsdk/1.25.2/1.25.3) | --- ### Release Notes <details> <summary>modelcontextprotocol/typescript-sdk (@​modelcontextprotocol/sdk)</summary> ### [`v1.25.3`](https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/v1.25.3) [Compare Source](modelcontextprotocol/typescript-sdk@v1.25.2...v1.25.3) #### What's Changed - \[v1.x backport] Use correct schema for client sampling validation when tools are present by [@​olaservo](https://github.com/olaservo) in [#​1407](modelcontextprotocol/typescript-sdk#1407) - fix: prevent Hono from overriding global Response object (v1.x) by [@​mattzcarey](https://github.com/mattzcarey) in [#​1411](modelcontextprotocol/typescript-sdk#1411) **Full Changelog**: <modelcontextprotocol/typescript-sdk@v1.25.2...v1.25.3> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi45NC4zIiwidXBkYXRlZEluVmVyIjoiNDIuOTQuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==--> Co-authored-by: Renovate Bot <renovate@boringstudio.by> Co-authored-by: ChubbChubbs <sgmakgg@gmail.com> Reviewed-on: https://git.boringstudio.by/BoringStudio/mcp-gitea/pulls/17 Co-authored-by: boring-bot <bot@boringstudio.by> Co-committed-by: boring-bot <bot@boringstudio.by>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backport of #1347 to v1.x branch for inclusion in a v1.x.x point release.
Fix client-side sampling validation to use
CreateMessageResultWithToolsSchemawhen tools are present in the request, preventing false validation failures for tool_use responses.Motivation and Context
When a client sampling handler returns
tool_usecontent formatted as an array, validation fails with "Invalid input: expected object, received array". This occurs because the client always validates againstCreateMessageResultSchemaregardless of whether tools were included in the request.CreateMessageResultSchemaexpects single content blocks (text, image, or audio only)CreateMessageResultWithToolsSchemasupports array content with tool_use/tool_result blocksThis mirrors the server-side fix from PR #1156, which the client-side code missed.
Fixes#1346
How Has This Been Tested?
Added 5 new integration tests in
test/client/index.test.ts:[{ type: 'tool_use', ... }]toolChoicealso triggers the correct schemaAll tests pass.
Breaking Changes
None
Types of changes
Checklist
🦉 Generated with Claude Code
Co-Authored-By: Claude Opus 4.5 noreply@anthropic.com