MCP get_message: clamp max_chars above 4000 to cap#12
Closed
endolith wants to merge 1 commit into
Closed
Conversation
Values above maxBodyChars (4000) previously fell back to the default (2000). Now they clamp to the cap like limitArg does for list limits. Zero or negative values still use the default. Co-authored-by: endolith <endolith@gmail.com>
Owner
Author
|
Close in favor of #15 |
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.
Summary
Fixes ambiguous
get_messagemax_charsboundary behavior: values above 4000 now clamp to the cap (4000) instead of silently falling back to the default (2000).Changes
max_chars > 4000→ clamp to 4000max_chars <= 0→ use default 2000 (unchanged)