Token-efficient query result encoding #55
Merged
Conversation
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
emanb29
pushed a commit
to hydrolix/mcp-hydrolix
that referenced
this pull request
Aug 14, 2025
(cherry picked from commit f9b5177)
emanb29
pushed a commit
to hydrolix/mcp-hydrolix
that referenced
this pull request
Sep 3, 2025
(cherry picked from commit f9b5177)
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.
The current query result duplicates the column names in every returned row. This can lead to a lot of tokens used by duplicated data. Specifying (ordered) column list with the rows should be sufficient context for models (especially given they are given the create table statement from one of the other tools)