fix: Update context logging type hints to match MCP spec #400
+79
−13
Conversation
This file contains 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
…ct before adding mcp dependency. (modelcontextprotocol#408)
…akib-hosen/python-sdk into fix/397-context-logging-types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
According to the MCP spec, context logging functions should accept any JSON-serializable type as the message parameter.
#397
How Has This Been Tested?
this has been tested with :
Integers (42)
Lists (["list", "of", "items"])
Dictionaries ({"key": "value"})
Floating point numbers (3.14)
string
Breaking Changes
None
Types of changes
Checklist