Add ValidationOptions for lenient output schema validation #1260
+281
−8
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
Currently, MCP clients raise
RuntimeError
when tools don't return structured content matching theiroutputSchema
. This breaks integrations with servers that have schema/implementation mismatches.This PR adds optional lenient validation that converts these errors to warnings, allowing clients to continue operating with imperfect servers.
How Has This Been Tested?
tests/client/test_validation_options.py
Breaking Changes
None. Default behavior unchanged. Lenient validation is opt-in:
Types of changes
Checklist
Additional context
ValidationOptions
class following existing patterns (e.g.,TransportSecuritySettings
)ClientSession.call_tool()
to check options before raising validation errorsstructured_output_lowlevel.py
by creating proper package structure