6.1.1.

Major Changes

Schema Complexity Reduction
Removed verbose parameter: Eliminated verbose fields from all tool schemas and implementations, reducing schema complexity
Simplified base schemas: Consolidated BaseBulkQueryItemSchema and BaseSingleQuerySchema into unified BaseQuerySchema
Streamlined parameter validation: Replaced complex flexible array schemas with simpler SimpleArraySchema utilities
Parameter Naming Standardization
Code Search: queryTerms → keywordsToSearch for clearer semantic meaning
Repository Search: Added topicsToSearch as separate parameter from keywordsToSearch
Commit Search: Updated to use keywordsToSearch consistently across all search tools
Tool Query Optimization
Repository Search Enhancement: Implemented automatic query expansion for searches containing both topicsToSearch and keywordsToSearch
Separated Search Strategies: Topics-based and keywords-based searches now run as separate optimized queries
Improved Search Precision: Enhanced filtering capabilities with clearer parameter descriptions
Schema Descriptor Improvements
Enhanced Documentation: More actionable and specific parameter descriptions
Better Validation: Improved Zod schema definitions with clearer constraints
Reduced Ambiguity: Eliminated nullable/optional complexity in favor of clear, simple types

🚀 Performance Enhancements
Token Efficiency
Removed verbose-only fields from responses when not needed
Simplified schema definitions reduce parsing overhead
Optimized bulk query processing with automatic query expansion
Search Optimization
Repository search now automatically separates topics and keywords into optimized parallel queries
Removed is:not-fork filter from repository quality filters for broader discovery
Enhanced match scope controls for more precise filtering

🔄 Breaking Changes
Parameter Renaming: queryTerms → keywordsToSearch (affects all search tools)
Verbose Parameter Removal: No longer supported across all tools
Schema Structure: Simplified base schemas may affect direct schema usage

🎯 Key Benefits
Reduced Token Usage: Simplified schemas and removed verbose fields significantly reduce token consumption
Better Search Results: Separated topics/keywords searches provide more targeted and comprehensive results
Improved Developer Experience: Clearer parameter names and descriptions enhance usability
Enhanced Performance: Optimized query processing and automatic expansion improve response times
Maintainability: Simplified schema structure makes future enhancements easier

🔮 Future Impact
This optimization lays the groundwork for:
More efficient AI assistant interactions
Better search result quality through specialized query strategies
Easier tool extension and maintenance
Reduced operational costs through token efficiency