Return all result sets from db_execute_query#126
Merged
nathanjcochran merged 1 commit intomainfrom Dec 12, 2025
Merged
Conversation
murrayju
approved these changes
Dec 12, 2025
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.
This is a follow-up to #123. In particular, see this comment thread.
Updates the
db_execute_querytool to return an array of result sets, instead of only the last result set. This makes it possible for the LLM to see the results of each statement in a multi-statement query, which can be useful in certain scenarios. Also includes the Postgres command tag with each result set, which should make it easier for LLMs to correlate the result sets with the individual SQL statements.I also made some small edits to some of the tool and field descriptions - mostly just making things more concise to avoid wasted tokens.