Enforce use of the "tree" parameter to reduce response size.#1
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the MCP tool input schema generation so that tools which support Jenkins “tree” pruning explicitly require a tree argument, guiding callers to use field selection to reduce oversized JSON responses.
Changes:
- Updates the
treeparameter description to clearly explain purpose and provide an example. - Marks
treeas a required input field (for tools where tree pruning is supported).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
kleincode
changed the title
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
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.
Currently, responses to most read-only tools are ridiculously large. To reduce response size, the optional "tree" parameter allows filtering the JSON response. However, this parameter is not used by the agent if not explicitly told so.
This PR marks the "tree" parameter as mandatory instead of optional, explains the purpose to the agent and gives an example.