feat: implement structured JSON response for search_docs tool - #10
Merged
Conversation
- Replace plain text response with structured JSON object using MCP structuredContent - Response now includes: instructions, search_terms, generalized_search_terms, path - Simplify instruction templates to be more concise and focused - Update SearchDocsResponse interface with correct field names - Update all tests to expect structured response format - Update architecture documentation to reflect new response format Breaking change: search_docs tool now returns structuredContent instead of text content
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
1 participant
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.
Breaking change: search_docs tool now returns structuredContent instead of text content