fix: omit structured_content when None instead of serializing as null #6499
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
The MCP spec defines
structuredContentas optional (field may be absent), not nullable:Without
skip_serializing_if, serde serializesOption::Noneasnullin JSON, but Zod's.optional()schema acceptsundefined(field absent) and rejectsnull.This was causing Zod validation errors in MCP Apps when calling tools that don't return structured content.
Changes
Added
#[serde(skip_serializing_if = "Option::is_none")]tostructured_contentfield inCallToolResponseso the field is omitted from JSON whenNone, aligning with the MCP spec.Related
Fixes #6454
See: #6454 (comment)