deepcontext

<tool> <purpose>Prepares a codebase for intelligent search by creating a searchable index</purpose> <when_to_use> <scenario>Call this first before searching any new codebase</scenario> <scenario>Required prerequisite for search_codebase</scenario> </when_to_use> <parameters> <parameter name="codebase_path" required="true"> <type>string</type> <description>ABSOLUTE path to the directory containing source code files</description> <examples> <valid>/Users/name/project</valid> <valid>/home/user/code/repo</valid> <invalid>.</invalid> <invalid>../project</invalid> <invalid>relative/path</invalid> </examples> <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation> </parameter> <parameter name="force_reindex" required="false"> <type>boolean</type> <description>Force complete reindexing even if already indexed</description> <default>false</default> <when_to_use>Code has changed significantly or search results seem outdated</when_to_use> </parameter> </parameters> </tool>

<tool> <purpose>Finds relevant code in an indexed codebase using natural language or keyword queries</purpose> <when_to_use> <scenario>Find specific functions, classes, or code patterns</scenario> <scenario>Get context before making changes to understand dependencies</scenario> <scenario>Explore how existing systems work</scenario> <scenario>Locate examples of API usage or patterns</scenario> </when_to_use> <parameters> <parameter name="query" required="true"> <type>string</type> <description>Natural language or keyword search query describing what code to find</description> </parameter> <parameter name="codebase_path" required="true"> <type>string</type> <description>ABSOLUTE path to the codebase directory to search</description> <examples> <valid>/Users/name/project</valid> <valid>/home/user/code/repo</valid> <invalid>.</invalid> <invalid>../project</invalid> <invalid>relative/path</invalid> </examples> <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation> </parameter> <parameter name="max_results" required="false"> <type>number</type> <description>Maximum number of code chunks to return</description> <default>5</default> <best_practice>Keep at default 5 for focused results. Use multiple targeted searches rather than increasing this limit</best_practice> </parameter> </parameters> <strategy> <guideline>Use specific technical terms: "authentication middleware", "database connection", "error handler"</guideline> <guideline>Focus on implementation: "user login function" rather than "user management system"</guideline> <guideline>Include file types when relevant: "SQL migration", "React component", "API endpoint"</guideline> </strategy> <workflow> <step>Search discovers relevant files and entry points, use imports and exports to find related files</step> <step>Use Read tool to explore discovered files in detail for complete implementation</step> <step>Use Grep tool for precise pattern matching of specific symbols or exact text</step> <step>Follow imports/exports from results to guide next searches</step> <step>Prefer multiple focused searches with 5 results over single large searches</step> <step>Search provides discovery, not complete solutions</step> </workflow> <result_interpretation> <point>Results ranked by semantic relevance, not code importance</point> <point>Implementation code often appears in results 2-5, not just #1</point> <point>Look for actual code files (.ts, .js, .sql) over documentation (.md, .txt)</point> </result_interpretation> <limitations> <limitation> <description>May miss foundational type definitions</description> <solution>Use Grep for "interface PluginName"</solution> </limitation> <limitation> <description>Shows implementations, not core contracts</description> <solution>Follow up with Read for full context</solution> </limitation> <limitation> <description>Semantic chunks may lack architectural hierarchy</description> <solution>Manual file exploration needed</solution> </limitation> <limitation> <description>Excludes filtered content: test files, generated code, config files, minified files, large data files</description> <solution>Use Grep tool to search test files (*.test.*, *.spec.*, __tests__, /tests/), config files, or generated content</solution> </limitation> <limitation> <description>For precise symbol search</description> <solution>Use Grep tool for exact matches</solution> </limitation> </limitations> <returns>Code chunks with file paths, line numbers, relevance scores, symbol information, imports, and exports</returns> <prerequisites>Codebase must be indexed first with index_codebase</prerequisites> </tool>

<tool> <purpose>Check if codebases are indexed and get their status information</purpose> <enhanced_features> <feature>Shows completion statistics for finished indexing (success rates, processing time, performance metrics)</feature> <feature>Displays batch processing details (successful/skipped batches)</feature> <feature>References log files for detailed debugging</feature> </enhanced_features> <when_to_use> <scenario>Before indexing to check if already done</scenario> <scenario>After indexing to see completion statistics and success rates</scenario> <scenario>Debug why search returned no results</scenario> <scenario>Confirm indexing completed successfully</scenario> <scenario>Get overview of all indexed codebases</scenario> </when_to_use> <parameters> <parameter name="codebase_path" required="false"> <type>string</type> <description>ABSOLUTE path to specific codebase to check</description> <examples> <valid>/Users/name/project</valid> <valid>/home/user/code/repo</valid> <invalid>.</invalid> <invalid>../project</invalid> <invalid>relative/path</invalid> </examples> <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation> <optional_behavior>Omit to get status of all indexed codebases</optional_behavior> </parameter> </parameters> <returns>Enhanced indexing status with completion statistics when available</returns> </tool>

<tool> <purpose>Permanently removes all indexed data for a codebase</purpose> <when_to_use> <scenario>Clear stale data before reindexing after major code changes</scenario> <scenario>Remove old indexed codebases no longer needed</scenario> <scenario>Fix corrupted index causing search issues</scenario> </when_to_use> <parameters> <parameter name="codebase_path" required="false"> <type>string</type> <description>ABSOLUTE path to the codebase to clear</description> <examples> <valid>/Users/name/project</valid> <valid>/home/user/code/repo</valid> <invalid>.</invalid> <invalid>../project</invalid> <invalid>relative/path</invalid> </examples> <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation> <optional_behavior>Omit to clear ALL indexed codebases (use with caution)</optional_behavior> </parameter> </parameters> <warnings> <warning>Destructive operation. All search capabilities lost until reindexing</warning> </warnings> </tool>