You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was discovered while reviewing PR #895. Besides CallToolResult, ToolResultContent should also be typed with its structured content as Option<Value> to accommodate any JSON value.
2025-11-25
2026-07-28
How Has This Been Tested?
Added tests
Breaking Changes
Yes. The public field ToolResultContent.structured_content changes type from Option<JsonObject> to Option<Value>.
The reason will be displayed to describe this comment to others. Learn more.
Worth one that loops through all the possible primitive types (string, number, boolean, null) and does the same test? This way it would catch if anyone changes it in some way that drops support for something.
The reason will be displayed to describe this comment to others. Learn more.
Good call, @alexhancock. I've opened #931 to bring in rstest for these repeated rmcp unit-test clusters (it also clears the existing -D warnings clippy failures on the test targets). Once #931 lands I'll come back and parametrize this with rstest so each primitive shows up as its own reported case.
Re-applies #919 (reverted by #932): ToolResultContent.structured_content
becomes Option<Value> so non-object structured content is accepted,
matching CallToolResult and SEP-2106.
BREAKING CHANGE: ToolResultContent.structured_content changes from
Option<JsonObject> to Option<Value>.
Re-applies #919 (reverted by #932): ToolResultContent.structured_content
becomes Option<Value> so non-object structured content is accepted,
matching CallToolResult and SEP-2106.
BREAKING CHANGE: ToolResultContent.structured_content changes from
Option<JsonObject> to Option<Value>.
Re-applies #919 (reverted by #932): ToolResultContent.structured_content
becomes Option<Value> so non-object structured content is accepted,
matching CallToolResult and SEP-2106.
BREAKING CHANGE: ToolResultContent.structured_content changes from
Option<JsonObject> to Option<Value>.
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
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.
Motivation and Context
This was discovered while reviewing PR #895. Besides
CallToolResult,ToolResultContentshould also be typed with its structured content asOption<Value>to accommodate any JSON value.How Has This Been Tested?
Added tests
Breaking Changes
Yes. The public field
ToolResultContent.structured_contentchanges type fromOption<JsonObject>toOption<Value>.The green SemVer Check is a false negative due to known upstream gap: obi1kenobi/cargo-semver-checks#148
Types of changes
Checklist