Allow arbitrary types in model creation by updating config in create_model#1132
Closed
coolbeevip wants to merge 1 commit intomodelcontextprotocol:mainfrom
Closed
Allow arbitrary types in model creation by updating config in create_model#1132coolbeevip wants to merge 1 commit intomodelcontextprotocol:mainfrom
coolbeevip wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
3 tasks
3 tasks
18 tasks
Member
|
What are toolkit functions? Please share an MRE. |
Author
|
Hey! I just noticed that the example at https://github.com/modelcontextprotocol/python-sdk/blob/main/examples/snippets/servers/images.py actually solves my issue. I'll go ahead and close this PR. Thanks! |
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 free
to 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.
Allow Pydantic models for toolkit outputs to use
arbitrary_types_allowed=Truein MCP/fastMCPFixes #1131
Motivation and Context
Without this change, registering toolkit functions with non-standard output types (e.g. third-party objects) leads to Pydantic schema generation errors.
How Has This Been Tested?
Tested by registering and calling toolkit functions returning non-standard types; tool registration and function invocation now work as expected.
Breaking Changes
No breaking changes.
Types of changes
Checklist
Additional context